3 ms·
Sometimes with heavily DB bound apps, it's a performance/scalability issue. Doubly so if the app's DB relies on aggressive locking for most/all of its transacti
by acveilleux 11y ago
Sometimes with heavily DB bound apps, it's a performance/scalability issue. Doubly so if the app's DB relies on aggressive locking for most/all of its transactions. You can do it with clouds but you often pay through the nose for the adequate storage (or cheat with 512GB of RAM these days.)
I've seen folks spend 3-4x more money (almost all of the excess to the SAN vendor) to get a VMware setup (because snapshots and VMotions) with the same reliable I/O a commodity Dell server with a 4-disks SAS Raid-10 and a decent RAID controller can deliver, not even talking SSDs here.
- toyg 11y agoSo much this. We always said to use "the right tool for the right job", isn't it? There are a lot of apps for which virtualized infrastructure is just not a good fit from a technical standpoint. When these end up in the cloud because suits decided OpEx is sweeter than CapEx, they suffer horribly; the customer ends up paying more (because prolonged I/O spikes in the cloud can be hugely expensive), the application runs slower than it did 5 years ago on commodity hardware, and nobody is happy. Still, suits decided cloud it must be, so cloud it will be. Sometimes the IT sector is depressing.