Well presumably they need only 1/3 of a developer to do this and they intend to scale up 10x in the next 5 years.
$60,000 per year in-house vs $1,200,000 per year aurora. No brainer really.
$60,000 per year in-house vs $1,200,000 per year aurora. No brainer really.
Note 'instances' eg plural, versus a singular EBS. There is some ambiguity here, I'm not sure where the 10x came from, but it seems plausible.
i saved hundreds of dollars per month by switching from an audi a4 to riding a home-built bike for my 1.5 mile commute to work
It really bugs me how everyone has drank the coolaide. Cloud is stupid expensive, but of course this is cloud vs cloud.
SANs add latency, who knew? What did surprise me during testing is that Aurora seems to have added latency even if the entire dataset could easily fit into buffers, with zero disk reads required.
If you want actually fast cloud DBaaS, the only way is with instances that have local NVMe for caching, like AWS ??gd.db instances.