News for hackers. Stuff that matters.
Re:We've saved 5000% in cloud costs by writing our own database by preommr on Saturday April 06, 2024 @01:48PM (#39954067)
I feel like the word "database" is throwing people off because they're comparing it with something like MySql/Postgres, when this seems slightly more complex than a k/v store stored to a file, with some other indexing, where data integrity is a low priority. That shouldn't take too much time and should be fairly isolated on the tech side so little involvement from product/project managers.
Re:We've saved 5000% in cloud costs by writing our own database by hmottestad on Saturday April 06, 2024 @02:13PM (#39954276)
A k/v store typically is really fast at looking up the value based on the key. So there are usually some pretty advanced indexes involved.
Re:We've saved 5000% in cloud costs by writing our own database by arandomusername on Saturday April 06, 2024 @03:12PM (#39954662)
or a simple b-tree...
Re:We've saved 5000% in cloud costs by writing our own database by eatonphil on Saturday April 06, 2024 @04:41PM (#39955304)
My simple btrees have had bugs in them. :)

(Though to be fair, if I actually wanted to put this in prod it probably wouldn't take too long to fuzz it and fix the kinks.)

https://github.com/eatonphil/btree-rs

Re:We've saved 5000% in cloud costs by writing our own database by paulddraper on Saturday April 06, 2024 @04:08PM (#39955056)
80/20
Re:We've saved 5000% in cloud costs by writing our own database by ozr on Saturday April 06, 2024 @11:30PM (#39957966)
For a k/v store, a hash table will take you very, very far.