_(2025/01/12) #sqlite TlDR; if you are running a homelab just use SQLite. Can I just be open and say that I that I absolutely adore SQLite? You know why? Because SQLite is just a file which is what makes it so magical. If I have to migrate or copy an application that uses SQLite, I simply drag and drop my files to where I want them to go and then I am done. If I am using a more enterprise database, such as Postgres, then I have to properly plan a database migration and then follow all the proper steps religiously (stop the database properly, export the database, etc.) or I will have drama with my data. I also never have to upgrade my database to a newer version as SQLite and the application that is utilizing SQLite handles that for me. I am not anti spinning up a "proper" and independent database for an application but for the homelab user, one can fulfill 99% of their needs by using SQLite and avoiding the maintenance overhead of dealing with an additional database container. I would even argue that for most businesses they could get away with running SQLite if their application is only going be used by a dozen people. I am not sure what the real threshold is when one decides to switch from SQLite to a more enterprise database but that usually occurs when performance and redundancy is paramount; one can always deploy your application with SQLite then cutover to something like Postgres later on. Further reading and discussion about SQLite: * https://news.ycombinator.com/item?id=38036921 * https://news.ycombinator.com/item?id=31152490