0%

Where to Go Next

Choose Your Next Database Route

A new database tool is useful when it solves a problem your SQLite project does not have. Start with that problem. Then choose one small project with a visible finish.

New problemRouteOne bounded project
Several processes or computers need one shared databasePostgreSQL and a client/server driverMove the three tables and the availability query to a local practice server.
Repeated mapping between rows and Python dominates the codeSQLAlchemy or another ORMMap the three tables and reproduce one query while still inspecting the SQL it generates.
Another program needs lending operations over HTTPA web APIExpose one read-only available-items endpoint around the existing query boundary.
Exploration and summaries are the main goalSQL and data-analysis toolsExport the activity rows and answer one grouped question about them.
One measured query is slow with much more dataIndexes and query plansCompare that query’s plan before and after one justified .
Protecting the data matters beyond application codeDatabase operationsBack up a disposable database, restore it elsewhere, and verify the restored rows.

Pick one route, not all six. Write down the problem, the first change, and the evidence that will mean the project is done. “Learn PostgreSQL” has no finish. “The three tables and availability query work through a local PostgreSQL server” does.

These routes also show what lies beyond the project you just built. You have not yet practiced installing or administering PostgreSQL or MySQL, hosted credentials and TLS, authentication, deployment, connection pools, concurrent writers, backups, performance tuning, indexes, EXPLAIN QUERY PLAN, ORM behavior, asynchronous drivers, or a web framework. Naming a subject is not the same as learning it.

That is good news for your next project: you do not need to pretend the whole database world is one step. Choose the new pressure you actually have, preserve the habits that already work, and add one new boundary at a time.