litefs-js VS postgresql-embedded

Fly[1] uses it

1: https://fly.io/blog/introducing-litefs/

Check this series of articles out: 1, 2, 3, 4, 5, 6, 7.

Also worth mentioning Fly.io's work on LiteStream [1] and LiteFS [2] giving SQLite important S3 DR/reliability & multi-node replication and scalability opens SQLite up to even more use-cases.

We're making use of this ourselves in https://blazordiffusion.com which runs entirely on SQLite, using Litestream to replicate it to Cloudflare's R2 object storage which is running on a single Hetzner US Cloud VM at €13 /mo.

As we believe SQLite + Litestream is a very cost effective solution that can support a large number of App's data requirements we've added first-class support to add SQLite + Litestream support in our Project templates [3] which uses GitHub Actions to run Docker compose App deployments along with setting up Litestream replication to AWS S3, Azure Blob Storage and SFTP in a sidecar container that also includes support running DB Migrations on Server with Rollback on failure. If anyone's looking to do something similar, the GitHub Actions that enable this are being maintained at [4].

[1] https://litestream.io

[2] https://fly.io/blog/introducing-litefs/

[3] https://docs.servicestack.net/ormlite/litestream

[4] https://github.com/ServiceStack/mix/tree/master/actions

> In contrast to many other database management systems, SQLite is not a client-server database engine, but you actually very rarely need that. If your application software runs on the same physical machine as the database, which is what most small to medium sized web applications does, then you probably only need SQLite.

Disagree.

If you think about it from an attack surface perspective, there are numerous advantages to isolating the database. There are performance, availability, sharding, and columnar options out there also that may better meet the use-case (just to name a few). I have ran Postgres on endpoints when developing with performance akin to SQLite. Further, there are numerous ways in which to increase performance, availability, or to pursue some of the more customized versions of Postgres depending on use-case. One of the times I used Postgres was with Oracle DBAs, and they found the transition pretty simple.

Various customizations / extensions / versions of PG

There are security versions e.g. https://www.crunchydata.com/products/hardened-postgres

Columnar / high performance Parallelized extensions e.g. https://www.citusdata.com/product

General Purpose / Oracle transitions e.g. https://www.citusdata.com/product

Yandex even has an embedded Postgres https://github.com/yandex-qatools/postgresql-embedded

If you'd like to see a full list of features see https://www.postgresql.org/about/featurematrix/

More than this though, PG has a really excellent community with a large amount of talented folks, available both individually and through OSS oriented companies https://www.postgresql.org/support/professional_support/ and willing to help out on Libera https://www.postgresql.org/about/news/migration-of-postgresq...

I think this is the component - away from laptop at the moment: https://github.com/yandex-qatools/postgresql-embedded

https://github.com/yandex-qatools/postgresql-embedded (no longer maintained)