- May 24, 2017
- 104
- 50
- Awards
- 2
- First Name
- Jason
One dealer said the reason for DDC going dark was that they were being "attacked"...not sure how much truth there is to it.
Even so, that's the price you pay to be one of the big boys, hire better people and security. Have a back-up plan. I mean... how much do they make?One dealer said the reason for DDC going dark was that they were being "attacked"...not sure how much truth there is to it.
If only there was a site provider that hosted every site on its own server.
Are you talking about Docker? Or are you using VMs?
I wish someone would calculate the amount of leads and money lost during the down time. A perfect time to switch to another vendor.
Ah yes, I should clarify and be careful with the 'server' term -- but yes, VMs for us.
Ouch....I agree with Alex - you would think if they cared about their clients, they would spend some cheddar on security /backup option.
In all fairness to Dealer.com I don't think we should paint them as uncaring. Everyone makes mistakes. They probably have one of the largest investments in security and backup in this industry. The teams allocated to those areas are bigger than some of their competitors' entire organization!
When you get as big as them it is harder to cover up the amount of shit when it hits the fan.
I can forgive them for little outages that get fixed. I would even forgive them for their 6+ month SEO issue if they'd pick up the damn phone or get back on DealerRefresh and continue to address it. That is uncaring! And definitely not the Dealer.com I once worked for.
It's a partial solution, but every VM is hosted on a host machine. If the host machine has a fault or a kernel failure, all your VMs go down at once either way. Live redundancies is the only way to truly avoid this issue, which requires separate bare metal servers, a load balancer or a docker/kubernetes build (which is what we use).
The Dealer.com one also sounds like a bad code deployment, so once again servers and VMs wouldn't stop that at all.
The solution for this is better QA process, which is incredibly complex when you have a product this widespread.
Bingo, I've said it before, they're too big for their britches. Scaling becomes a problem.It's a partial solution, but every VM is hosted on a host machine. If the host machine has a fault or a kernel failure, all your VMs go down at once either way. Live redundancies is the only way to truly avoid this issue, which requires separate bare metal servers, a load balancer or a docker/kubernetes build (which is what we use).
The Dealer.com one also sounds like a bad code deployment, so once again servers and VMs wouldn't stop that at all.
The solution for this is better QA process, which is incredibly complex when you have a product this widespread.