einnjo

I recently used SQLite in my side project [1]. Here's what I learned from using it:

* Shaving the overhead of network calls for queries sped up my site significantly.

* Most CI/CD providers include SQLite in their base linux images and setup in local envs is easy as well. Running tests against the actual database is simple.

* Replication is not available out of the box. To share a database with multiple instances of your app you will have to use a shared storage volume or some of the available solutions at [2][3][4], but they each come with their caveats.

[1] https://www.tendielist.com

[2] http://litereplica.io

[3] http://litesync.io

[4] https://bedrockdb.com

Built using the following tech stack:

- Node.js/Typescript

- Sqlite

- Fastify Framework (https://www.fastify.io/)

- HTMX (https://htmx.org/)

- Traefik for load balancing (https://traefik.io/)

- Nginx colocated with app for ssl termination and static assets.

- Umami as an alternative to Google Analytics (https://umami.is/)

- Cloudflare CDN

- Vultr for hosting

- Grafana Cloud with Loki for monitoring

Finally shipped my first side project. It tracks the most mentioned stock tickers on /r/WallStreetBets. It runs on Node.js/Typescript using server-side templates and SQLite.

I've dabbed in elixir and clojure for some time now and the ability to gain a REPL into a live system opens many opportunities for live debugging and introspection. It's a great tool when dealing with unknown states and bugs in production.