Well that depends. Are you going with micro services because it’s fashionable or because different parts of your backend work with completely different data and don’t need to communicate with eachother that much?
I’m of the opinion that anything that needs to share one database should be one service, and things that are so easily detached that you can just plop the tables over into a separate database, can be separate services, because that will allow you to scale up one without scaling the other and one database’s I/O won’t get in the way of the other database’s I/O (assuming they’re on different machines of course). I’d say:
My perspective is a self hosting hobbyist I noticed for those running on more reliable vps servers with rollbacks being a last resort the higher requirements are not as important.
That’s as a self-hosting hobbyist. Sqlite is great for that. It stops being great when you have thousands of users, and good luck using it with millions.
Compare frameworks more than languages.
Hyper > Gin > FastAPI > NextJS > Laravel > Drupal
Qt > GTK > Tauri > Fyne > Wails > Electron > React Native
Sqlite ~ Pgsql > mariadb
One docker container > ten micro services
Environment variables > ini > database config table
Edit: voters have spoken sqlite and pg are now on equal footing.
BRB, gonna tell my boss we should move our data warehouse to sqlite.
He said “simple comparisons of technologies on a single metric are stupid.”
Well that depends. Are you going with micro services because it’s fashionable or because different parts of your backend work with completely different data and don’t need to communicate with eachother that much?
I’m of the opinion that anything that needs to share one database should be one service, and things that are so easily detached that you can just plop the tables over into a separate database, can be separate services, because that will allow you to scale up one without scaling the other and one database’s I/O won’t get in the way of the other database’s I/O (assuming they’re on different machines of course). I’d say:
Microservices ~ monolith > Distributed monolith
Distributed monoliths suck.
Disagree. Different tools for different jobs.
My perspective is a self hosting hobbyist I noticed for those running on more reliable vps servers with rollbacks being a last resort the higher requirements are not as important.
That’s as a self-hosting hobbyist. Sqlite is great for that. It stops being great when you have thousands of users, and good luck using it with millions.