SQLite Internals: Pages and B-trees
I love this.<p>I have been a fan of SQLite for years, and it makes me genuinely happy to see other people have the same enthusiasm for the software.<p>A couple of years ago, during a job search, I came across a couple of companies that I thought were a good match. I went through the interview process with all of them and, due to similarities in the interview process, we ended up talking about the same thing: databases. Oh the horror in the interviewers’ eyes whenever I mentioned SQLite. Experienced software engineers from The New York Times, for example, went as far as to mock my engineering choices in 3 out of 5 interviews, despite the success of the products my team built on top of SQLite.<p>The experience made me feel awful and I stopped talking about SQLite for a couple of years. Instead, whenever someone asked a question about databases, I would answer with the PostgreSQL equivalent, knowing that the basic features are all the same.<p>That is why, whenever I see projects like Litestream [1][2] used by excellent products like Tailscale [3], it brings me joy.<p>A friend of SQLite is a friend of mine :-)<p>[1] <a href="https:&#x2F;&#x2F;litestream.io" rel="nofollow">https:&#x2F;&#x2F;litestream.io</a><p>[2] <a href="https:&#x2F;&#x2F;fly.io&#x2F;blog&#x2F;all-in-on-sqlite-litestream&#x2F;" rel="nofollow">https:&#x2F;&#x2F;fly.io&#x2F;blog&#x2F;all-in-on-sqlite-litestream&#x2F;</a><p>[3] <a href="https:&#x2F;&#x2F;tailscale.com&#x2F;blog&#x2F;database-for-2022&#x2F;" rel="nofollow">https:&#x2F;&#x2F;tailscale.com&#x2F;blog&#x2F;database-for-2022&#x2F;</a>