testeronious@lemmy.world to Programming@programming.dev · 7 months agoHow we’ve saved 98% in cloud costs by writing our own databasehivekit.ioexternal-linkmessage-square24fedilinkarrow-up193arrow-down14
arrow-up189arrow-down1external-linkHow we’ve saved 98% in cloud costs by writing our own databasehivekit.iotesteronious@lemmy.world to Programming@programming.dev · 7 months agomessage-square24fedilink
minus-squaredohpaz42@lemmy.worldlinkfedilinkEnglisharrow-up34·7 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-squareFalseMyrmidon@kbin.runlinkfedilinkarrow-up17·7 months agoI’m sure their custom database will be easy to find people to support and maintain
minus-squareFlaminGoku@reddthat.comlinkfedilinkarrow-up2·7 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.
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.