What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Bytes #226, published September 28, 2023, introduced Turso through a provocative question: what if an application used many small databases instead of putting every customer or project into one large shared database? The issue framed Turso as an edge-hosted, distributed database based on libSQL, then described as Turso’s open-source SQLite fork. Its examples were a database per project, SaaS customer, or user.
What is Turso?
In Bytes #226, Turso was presented as a way to use SQLite-style databases across distributed infrastructure. The issue’s explanation leaned on SQLite being a library and its databases being files, making it plausible to provision separate databases for individual projects, customers, or users rather than treating one shared database as the default.
As an Amazon Associate I earn from qualifying purchases.
In the interview, Turso CEO Glauber Costa put the idea this way: “We built our product around SQLite, which is really just a library.” That is Costa’s description in the September 28, 2023 issue, not a complete or necessarily current product definition.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Turso’s current product framing separates open-source software, its cloud offering, and embedded replication and sync. Its product overview describes those operating models; they should not be treated as interchangeable versions of the same deployment.
#1 Best Overall
- hardcover, brand new
Why use many databases?
The issue’s case for “many databases” is about data isolation and provisioning, not a claim that every application should replace tables with separate database files. A database per customer or project can make each unit’s data boundary explicit. The trade-off is that an application and its operations must manage a larger number of database instances.
- Per project: Keep one project’s data separate from another’s.
- Per SaaS customer: Give each tenant a distinct database rather than placing all tenants’ records in shared tables.
- Per user: A platform such as Val Town could assign each user an individual database.
The newsletter connected this approach’s low-friction potential partly to SQLite databases being files. That is the issue’s architectural rationale, not a universal guarantee of lower costs: actual cost and operational complexity depend on the product, usage, and hosting model.
Rank #2
- Brand: McGraw-Hill Education
- Database System Concepts, 7th Edition
What were Embedded Replicas?
In 2023, the issue described Embedded Replicas as a local SQLite database copy associated with a remote Turso database. The pitch was to pair local responsiveness with remote deployment. That framing matters: it described the mechanism discussed in the issue, not every current Turso sync capability.
Turso’s current embedded replication documentation describes replication and sync for local-first and offline-capable applications. For an app that needs local data access, the relevant questions are how it behaves without connectivity, how changes synchronize, and whether its write patterns fit the chosen model. The documentation, rather than the 2023 newsletter’s shorthand, is the appropriate source for current implementation details.
How have Turso’s database limits changed?
Bytes #226 reported that Turso’s free tier allowed up to 500 databases and that a $29-per-month tier included 10,000 databases. Those are historical figures reported by the newsletter in September 2023, not current plan guidance.
Turso’s current pricing page, accessed in 2026, lists 100 databases on Free and unlimited databases on paid self-serve plans. It also specifies usage allowances and paid overages. Prices and included usage vary by plan and billing selection, so check the live page for the terms that apply before choosing a plan.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What should a developer decide before choosing an approach?
The issue’s central question—why a front-end developer should care about databases—has a practical answer: the data model and operating model affect how an application separates users’ data and behaves when it is offline or far from a server. Choosing among shared storage, many isolated databases, a hosted cloud database, or an embedded local database depends on the application rather than a universal rule.
- Isolation: Decide whether projects, tenants, or users need distinct databases or can safely share one database with appropriate data boundaries.
- Connectivity: Determine whether the app must read or write locally while offline, or whether access through a hosted service is sufficient.
- Synchronization: For a local-first design, establish how local changes and remote data should synchronize.
- Compatibility and migration: Check whether SQLite compatibility and the application’s existing schema and migration approach fit the selected Turso mode.
- Operations and budget: Account for database count, usage limits, overages, and the work of managing many isolated databases.
These are distinct architectural options, not a ranking. Turso’s product materials establish that cloud and embedded/local-first approaches are available; they do not establish one as best for every workload.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
