SQLite: Protégé of PostgreSQL
Andrea Ross1 HN recommenders · 2014–2017
8K views · talk · evergreen · Uploaded 2014-05-31
D. Richard Hipp's PGCon 2014 keynote on SQLite's relationship to PostgreSQL. He explains that SQLite was originally written from PostgreSQL 6.5 documentation and that the two engines serve different classes of problems.
Recommended as a talk from SQLite's main author, and cited for the project's focus on backwards compatibility and for deployment anecdotes.
40:20"Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson
Strange Loop Conference
1:03:55🚀 TDD, Where Did It All Go Wrong (Ian Cooper)
DevTernity Conference
31:44The Value of Values with Rich Hickey
InfoQ
32:56Bret Victor The Future of Programming
Joey Reid
1:18:21"Uncle" Bob Martin - "The Future of Programming"
Paul Stringer's Mobile Tech
59:56AWS re:Invent 2018: Amazon DynamoDB Deep Dive: Advanced Design Patterns for DynamoDB (DAT401)
Amazon Web Services
58:39Tim Ewald - Clojure: Programming with Hand Tools
ClojureTV
47:43"Turning the database inside out with Apache Samza" by Martin Kleppmann
Strange Loop Conference
3 comments from Hacker News
As a read-only database, sqlite doesn't have too many limits, since the storage mechanism is flexible enough to allow fast queries. The problem comes when you start writing, and reads have to wait for them. Also, (I believe) it was this talk [VIDEO] that mentions sqlite being used in adobe lightroom, and it being faster to access thumbnails from an sqlite database.
Not sure about a 30 year timeframe. 10 years seems like it wouldn't be any kind of problem (personal opinion), but 30 years is an awful long time. That being said, the SQLite development Community are very very big on backwards compatibility. eg: [VIDEO] Hmmmm, there's a better talk by D. Richard Hipp around, but I'm not finding it atm. In the better talk he explains they (SQLite) are planning to be around for the 30 year timeframe you mention. Something to do with an airplane manufacturer looking for long term guarantees, but I don't remember the details.
AFAIK SQLite doesn't achieve atomicity by virtue of its global write lock. It does so by using a rollback journal (default) or WAL. So it's not really all that different from PostgreSQL in that regard and the authors point remains valid :). You might also enjoy this talk by the main author of SQLite: [VIDEO] (SQLite: Protégé of PostgreSQL)