--- title: Why Two Engineers Maintain the World's Most-Used Database description: SQLite, created by Richard Hipp in 2000 while working on Navy destroyer software, has become the most deployed database engine in history with an estimated... canonical: https://daily.dev/posts/why-two-engineers-maintain-the-world-s-most-used-database-yaprnhlxl twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why Two Engineers Maintain the World's Most-Used Database | daily.dev og:description: SQLite, created by Richard Hipp in 2000 while working on Navy destroyer software, has become the most deployed database engine in history with an estimated... og:url: https://daily.dev/posts/why-two-engineers-maintain-the-world-s-most-used-database-yaprnhlxl og:image: https://api.daily.dev/og/posts/yaPrnhLXL.png og:image:alt: Why Two Engineers Maintain the World's Most-Used Database og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why Two Engineers Maintain the World's Most-Used Database **[ByteMonk](https://daily.dev/sources/bytemonk)** · 8 min read · 7 upvotes · 2 comments ## Summary SQLite, created by Richard Hipp in 2000 while working on Navy destroyer software, has become the most deployed database engine in history with an estimated trillion+ active instances, far outpacing MySQL and Postgres installs. Unlike traditional client-server databases, SQLite is a serverless library that reads and writes directly to a single file, using B-tree structures for storage and write-ahead logging (instead of the original rollback journal) for crash-safe, ACID-compliant transactions. The engine compiles to roughly 300KB, is built from about 160,000 lines of C code backed by around 90 million lines of test code (a 600:1 test-to-code ratio), achieves 100% MC/DC branch coverage, and is certified under the DO-178B avionics safety standard. Remarkably, only two full-time engineers maintain it. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How does SQLite achieve crash safety without a database server? SQLite uses write-ahead logging (WAL) instead of directly modifying its main database file. Changes are appended to a separate WAL file, and a commit marker is written there when a transaction commits; the main file is later updated during a checkpoint. This means readers and writers don't block each other, writes are sequential and fast, and uncommitted WAL entries are simply ignored on crash recovery, keeping the main file always consistent. _daily.dev surfaces deep dives like this for developers reasoning about durability trade-offs in embedded storage._ ### How many people maintain SQLite and how thoroughly is it tested? SQLite, used in an estimated over a trillion active deployments, is maintained by just two full-time engineers. Its core is about 160,000 lines of C, backed by roughly 90 million lines of test code, a ratio of about 600 lines of test per line of source. This testing achieved 100% MC/DC coverage, the modified condition/decision coverage standard used for avionics software, and SQLite is certified under DO-178B for use in commercial aircraft. _engineers evaluating embedded database reliability can find this kind of technical detail on daily.dev._ ### What is the difference between SQLite and a traditional server-based database like PostgreSQL? SQLite is a library linked directly into an application rather than a separate server process; there's no network connection, no ports, and no configuration, just a single file on disk that the linked code reads and writes directly. PostgreSQL and MySQL require a running server process that manages connections, memory, and caching over a network. Despite its simplicity, SQLite remains fully ACID compliant with working transactions and crash safety. _developers weighing embedded versus server databases can track these architecture comparisons on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@pdfopsdev** · 1 upvotes > wal mode doing the heavy lifting there, readers never block writers so you get real concurrency without a server process running. **@trevorsuna** · 0 upvotes > SQLite’s tiny maintainer count is less alarming when paired with its unusually deep test discipline and narrow deployment model. The useful takeaway is not that every project needs a 600:1 test ratio, but that boring compatibility promises require sustained, automated evidence. ## Similar posts on daily.dev - [100000 TPS over a billion rows: the unreasonable effectiveness of SQLite](https://daily.dev/posts/100000-tps-over-a-billion-rows-the-unreasonable-effectiveness-of-sqlite-pslxym1dd) · Hacker News · 2 upvotes · 0 comments - [SQLite for Everything](https://daily.dev/posts/sqlite-for-everything-rupb2mkye) · Lobsters · 7 upvotes · 1 comments --- Tags: [#testing](https://daily.dev/tags/testing), [#backend](https://daily.dev/tags/backend), [#sqlite](https://daily.dev/tags/sqlite) [View this post on daily.dev](https://daily.dev/posts/why-two-engineers-maintain-the-world-s-most-used-database-yaprnhlxl) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Why Two Engineers Maintain the World's Most-Used Database","url":"https://daily.dev/posts/why-two-engineers-maintain-the-world-s-most-used-database-yaprnhlxl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-two-engineers-maintain-the-world-s-most-used-database-yaprnhlxl"},"datePublished":"2026-08-25T03:24:42.874Z","dateModified":"2026-09-13T19:21:16.712Z","description":"SQLite, created by Richard Hipp in 2000 while working on Navy destroyer software, has become the most deployed database engine in history with an estimated...","image":"https://i.ytimg.com/vi/zzaj4ueQe8U/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/zzaj4ueQe8U/sddefault.jpg","isAccessibleForFree":true,"articleSection":"ByteMonk","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ByteMonk","logo":"https://media.daily.dev/image/upload/s--n36_-Uve--/f_auto/v1752670492/logos/bytemonk","url":"https://daily.dev/sources/bytemonk"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/why-two-engineers-maintain-the-world-s-most-used-database-yaprnhlxl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":7},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"testing,backend,sqlite","timeRequired":"PT8M","video":{"@type":"VideoObject","name":"Why Two Engineers Maintain the World's Most-Used Database","description":"SQLite, created by Richard Hipp in 2000 while working on Navy destroyer software, has become the most deployed database engine in history with an estimated...","thumbnailUrl":"https://i.ytimg.com/vi/zzaj4ueQe8U/sddefault.jpg","uploadDate":"2026-08-25T03:24:42.874Z","duration":"PT8M","url":"https://api.daily.dev/r/yaPrnhLXL","embedUrl":"https://www.youtube.com/embed/zzaj4ueQe8U"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ByteMonk","item":"https://daily.dev/sources/bytemonk"},{"@type":"ListItem","position":3,"name":"Why Two Engineers Maintain the World's Most-Used Database"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/why-two-engineers-maintain-the-world-s-most-used-database-yaprnhlxl","comment":[{"@type":"Comment","text":"wal mode doing the heavy lifting there, readers never block writers so you get real concurrency without a server process running.","datePublished":"2026-08-25T18:11:54.974Z","url":"https://daily.dev/posts/yaPrnhLXL#c-vG9ITTx7k","author":{"@type":"Person","name":"PDFops","url":"https://daily.dev/pdfopsdev","image":"https://media.daily.dev/image/upload/s---8isRBKc--/f_auto/v1782922291/avatars/avatar_orjMeK8QKaaVZwGq7ScPz?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"SQLite’s tiny maintainer count is less alarming when paired with its unusually deep test discipline and narrow deployment model. The useful takeaway is not that every project needs a 600:1 test ratio, but that boring compatibility promises require sustained, automated evidence.","datePublished":"2026-08-26T02:44:27.017Z","url":"https://daily.dev/posts/yaPrnhLXL#c-6V9UWc20K","author":{"@type":"Person","name":"Trevor Suna","url":"https://daily.dev/trevorsuna","image":"https://media.daily.dev/image/upload/s--dZ7gXxpp--/f_auto/v1784081551/avatars/avatar_EMoP47rpuw8DNjhp6R1b6?_a=BAMAMicg0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/why-two-engineers-maintain-the-world-s-most-used-database-yaprnhlxl#faq","mainEntity":[{"@type":"Question","name":"How does SQLite achieve crash safety without a database server?","acceptedAnswer":{"@type":"Answer","text":"SQLite uses write-ahead logging (WAL) instead of directly modifying its main database file. Changes are appended to a separate WAL file, and a commit marker is written there when a transaction commits; the main file is later updated during a checkpoint. This means readers and writers don't block each other, writes are sequential and fast, and uncommitted WAL entries are simply ignored on crash recovery, keeping the main file always consistent. daily.dev surfaces deep dives like this for developers reasoning about durability trade-offs in embedded storage."}},{"@type":"Question","name":"How many people maintain SQLite and how thoroughly is it tested?","acceptedAnswer":{"@type":"Answer","text":"SQLite, used in an estimated over a trillion active deployments, is maintained by just two full-time engineers. Its core is about 160,000 lines of C, backed by roughly 90 million lines of test code, a ratio of about 600 lines of test per line of source. This testing achieved 100% MC/DC coverage, the modified condition/decision coverage standard used for avionics software, and SQLite is certified under DO-178B for use in commercial aircraft. engineers evaluating embedded database reliability can find this kind of technical detail on daily.dev."}},{"@type":"Question","name":"What is the difference between SQLite and a traditional server-based database like PostgreSQL?","acceptedAnswer":{"@type":"Answer","text":"SQLite is a library linked directly into an application rather than a separate server process; there's no network connection, no ports, and no configuration, just a single file on disk that the linked code reads and writes directly. PostgreSQL and MySQL require a running server process that manages connections, memory, and caching over a network. Despite its simplicity, SQLite remains fully ACID compliant with working transactions and crash safety. developers weighing embedded versus server databases can track these architecture comparisons on daily.dev."}}]} ```