Other databases have the same issue, try having multiple database containers (without massive speed losses). If application is bound by the performance of the front end, this is a problem, but those really are not what SQLite was intended for.
In the case of database bound applications, SQLite is just as good as any other database, which despite having a client server model can typically only handle a single operation at once.
In a world of containers and stateless applications, fuck SQLite.
You can always use sqlite cloud
/s?
… you know you can put SQLite in a container right? It doesn’t even need to be persisted to disk - it can just live in RAM.
If you don’t care about persistence, why are you even using a DB in the first place?
Just learn how to configure your containers.
Please teach me how to configure my containers so SQLite can scale horizontally.
deleted by creator
Other databases have the same issue, try having multiple database containers (without massive speed losses). If application is bound by the performance of the front end, this is a problem, but those really are not what SQLite was intended for.
In the case of database bound applications, SQLite is just as good as any other database, which despite having a client server model can typically only handle a single operation at once.
You misunderstood. I’m not talking about scaling the DB horizontally, I’m talking about scaling the application using the DB horizontally.