@[email protected] to Programming • 6 months agoHow we’ve saved 98% in cloud costs by writing our own databasehivekit.iomessage-square24fedilinkarrow-up193arrow-down14
arrow-up189arrow-down1external-linkHow we’ve saved 98% in cloud costs by writing our own databasehivekit.io@[email protected] to Programming • 6 months agomessage-square24fedilink
minus-square@[email protected]linkfedilink7•6 months ago What has changed though, is that we’ve replaced our $10k/month Aurora instances with a $200/month Elastic Block Storage (EBS) volume. Holy shit, I hope whoever wrote this gets a fat bonus at the end of the year. That’s a truly astounding savings.
minus-square@[email protected]linkfedilinkEnglish34•6 months agoWhat they don’t say is how much in developer time they’ve spent rolling their own database. Then there’s also maintenance and new features.
minus-squareFalseMyrmidonlinkfedilink17•6 months agoI’m sure their custom database will be easy to find people to support and maintain
minus-square@[email protected]linkfedilink2•6 months agoIt seems like features would be mainly additional key/values like temperature, humidity, etc. This wouldn’t really change the underlying infrastructure greatly but still give good enhancements to certain customers.
Holy shit, I hope whoever wrote this gets a fat bonus at the end of the year. That’s a truly astounding savings.
What they don’t say is how much in developer time they’ve spent rolling their own database. Then there’s also maintenance and new features.
It’s called job security, bro.
I’m sure their custom database will be easy to find people to support and maintain
It seems like features would be mainly additional key/values like temperature, humidity, etc. This wouldn’t really change the underlying infrastructure greatly but still give good enhancements to certain customers.