Welcome to another VSHN.timer! Every Monday, 5 links related to Kubernetes, OpenShift, CI / CD, and DevOps; all stuff coming out of our own chat system, making us think, laugh, or simply work better.
This week we’re going to talk about this wonderful thing in the public domain called SQLite, and its various uses.
1. We have already published a VSHN.timer issue dedicated to SQLite (that was #138) but clearly we’re not the only ones in awe. Nikos Vaggalis published a nice summary of the best things in SQLite, and there’s a lot to like: SQLite is cross-platform, supports lots of programming languages, is portable, and is backward-compatible. Oh, and it’s in the public domain, too.
2. SQLite uses its own built-in virtual machine, to process queries and access data in a uniform way, no matter which operating system or programming language we’re using. Ben Johnson of Fly.io explains how the SQLite virtual machine works with an easily understandable article that doesn’t require you to have a Ph.D. in computer science. Oh, and Fly.io has also recently introduced LiteFS, an open-source distributed file system for SQLite. Check it out!
3. You might be surprised by reading this, but no, the SQLite project is not stored in a Git repository. The SQLite team has built (and open-sourced) its own version control system, called Fossil, and it has quite a few differences from Git; for example, Fossil stores changesets in a… SQLite database! The always interesting Matt Rickard explains Fossil in his blog.
4. Do you store SQLite files in S3 buckets? Would you like to be able to run
SELECT queries against those databases? Wish no more, for s3sqlite is here to help you do exactly that.
5. Marmot is a distributed SQLite replicator that uses NATS, providing robust recovery and replication of your database files, and enabling your website to handle lots of traffic without issues.
Have you tried replacing Git with Fossil? Are you replicating your SQLite databases in production? Would you like to share some SQLite tips and tricks with our readers? Get in touch with us, and see you next week for another edition of VSHN.timer.
PS: would you like to receive VSHN.timer every Monday in your inbox? Sign up for our weekly VSHN.timer newsletter.
PS2: do you prefer reading VSHN.timer in your favorite RSS reader? Subscribe to this feed.
PS3: check out our previous VSHN.timer editions about databases and storage: #111, #115, and #138.