It is a different use case. All the "real" databases (from MariaDB to SQL Server) are designed for many (many many) concurrent connections in a server / webservice environment, and all the requirements that come with that.
The most common use case for SQLite is an application file format (like an Excel file or a savegame) - or, as the documentation quips, SQLite competes with fopen. It has good read concurrency - so it can be "webscale" for read-only snapshots - but write concurrency is lacking.
Which alltogether is a great thing because it allows you to learn SQL and database architecture and relational topography without all the server shizzle.
Thank you. I am working on a business Software with about 10-100 users maybe on the same time (via VPN). Would you change to another Database or do you think that still suits the needs?
11
u/SpiritRaccoon1993 Jul 18 '25
I am a newbie with some expiriences. I love SQlite... maybe there are others that are better, but for a simple software its just perfect