If your software needs a database, you should always have a #SQLite option. This makes it far easier to offer your software as a simple #container or flatpak that is completely self-contained. I promise you, in 90% of the cases, that is sufficient. I know you all aim for super big scale deployments, but it almost always starts with a test install that should be as easy as possible to get up and running.
@jwildeboer Furthermore, with SQLite support available it's so much easier to write end-to-end tests that also run quickly so one doesn't get stupid ideas like ignoring them. :blobfoxwink:
@jwildeboer just keep this advise in mind: ask to your-hosting-provider-to-be of they offer this or not.
(Same with PostgreSQL)
It's rather disheartening to find out how obnoxious the some hosting providers can be about this topic!
@jwildeboer It takes substantial effort to support multiple database engines, unless programming framework is extremely abstract. SQLite is so basic - starting with datatypes, not even going to functions. Whenever I have a choice - PostgreSQL👍 :postgresql: Though I understand sadness of container nerds, who pack separate database instance in each container 🫣 Pack application - not the database! Otherwise serious problems will start as soon as there will be some real users :sql:
@jwildeboer Maybe it's just I 've seen too many systems that "just works" and never get properly refactored 🤷♂️ Until it breaks completely or hits serious flaw, nobody's ever going to invest an effort to improve :michael_scott:
There's a big market waiting for your software that always starts with the curiosity of a single person. If that person gets the immediate reward of a container pull and no-fuss working with your software — you win. If they first need to find a database, set up the connection and initialise etc — you lose.
@jwildeboer I still use containers only locally for testing stuff. It's the easiest way for me to test against several PostgreSQL versions.
I dropped Tiny Tiny RSS because I would have to have docker containers on a server.
Example: uptime-kuma. The container image JustWorks(tm) as it uses an embedded SQLite. A simple pull and run and you can start adding monitors. THIS is brilliant. https://github.com/louislam/uptime-kuma
Add comment