3 ms·
I wrote my own database once. It’s an “event sourcing” database, but I wrote it way before event sourcing was cool. It can handle over 1M events/sec on one core
by amluto 9y ago
I wrote my own database once. It’s an “event sourcing” database, but I wrote it way before event sourcing was cool. It can handle over 1M events/sec on one core. I don’t know any off-the-shelf product that could replace it.
I also helped write a log-structured OLTP-ish database that sits in front of MySQL.
I have only two regrets about these systems. First, MySQL was, in retrospect, the wrong backing store. Second, I used Thrift serialization. Thrift is not so great.
- dwyerm 9y agoDid using MySQL allow you to ship a product on-time and under budget? Or, to put this the other way, if you had used The Right Backing Store would you still have delivered the product in a timely manner at the right price-point?
- amluto 9y agoUnclear. I think the right backing store these days would be PostgreSQL. At the time, both were equally easy to get started with. PostgreSQL didn’t have fully serializable transactions yet (IIRC), and I was more familiar with MySQL. OTOH, MySQL has sucked in myriad ways. Replication is very easy to screw up. The query optimizer and SQL advanced feature support is not so good. In general, there have been a lot of rough edges.