A database for 2022
So to recap their timeline:<p><pre><code>  * Instead of an actual database use a JSON file.
  * Write a blog post about how that didn't scale.
  * Instead of an actual database hand-roll something else.
  * Write a blog post about how that didn't scale.
  * Instead of a database with built-in replication which is tailor built for key-value storage use SQLite with a single table containing key-value pairs and some fresh glue to make it replicate.
</code></pre>
I'm sorry, but what the fuck? Just writing the blog posts alone might have consumed more work-hours than what it would have taken to set a database up in the first place.<p>Are we supposed to expect another blog post somewhere around a year down the road titled "SQLite didn't scale" or "The new library for replication that was released a few months ago contained a bug that took our prod down"?