I developed a game with sqlite on the backend, during development sqlite took everything I threw at it. I planed to switch to mysql for production but when I b

I developed a game with sqlite on the backend, during development sqlite took everything I threw at it. I planed to switch to mysql for production but when I benchmarked sqlite it was able to do ~10,000 query's a second (iirc) way more than I needed so I figured I would try it in production. This was a mistake sqlite quickly died in production because of the amount of concurrent queries. During development it was just one processes using the database so locking wasn't a thing, but when more than one process was trying to use the same database waiting on locks slowed the whole thing to a stand still. I think its possible to write a client server protocol for sqlite with proper locks that performs as well as mysql, but it was easier to just use mysql :)