Don’t overthink it, use a SQL database for your next project
techmythos.substack.com
Don’t overthink it, use a SQL database for your next project
1–3 of 3 posts
Re: Don’t overthink it, use a SQL database for your next project
#2“Keep it simple”—something I keep repeating to everyone I work with. I myself have been bitten too often by the temptation to use the latest tech, even when a trusted but less “sexy” alternative was available that could do the job perfectly.
But this post could have been made a lot simpler by using SQLite. Do away with all the docker stuff, a simple file- based database will do for starters. If you need concurrent access later, it will be easy to port the DB to Postgres or similar.
Re: Don’t overthink it, use a SQL database for your next project
#3“Keep it simple”—something I keep repeating to everyone I work with. I myself have been bitten too often by the temptation to use the latest tech, even when a trusted but less “sexy” alternative was available that could do the job perfectly. But this post could have been made a lot simpler by using SQLite. Do away with all the docker stuff, a simple file- based database will do for starters. If you need concurrent ac…
I completely agree with the suggestion to use SQLite for simple projects, or even larger projects that need to be more portable.
Recently I've had some really great success using SQLite on an embedded project with decent enough support for concurrency using busy_timeout [https://www.sqlite.org/c3ref/busy_timeout.html] and WAL [https://www.sqlite.org/wal.html].