Our project utilizes a static database (no writes). With many users we don't actually have a problem per se reading it. If a database locks per read request by any user, then would it not be more efficient (though perhaps unnoticeable) to have multiple databases that each user connects to individually?We are database noobs. Apologies in advance if this is in the wrong place. We are planning on using BoltDB or LMDB for our project, but personally I was intrigued by this idea.
Identical Databases for Multiple Users Reading Efficiency
database;efficiency;golang
Unless your database is measured in Terabytes and your concurrent user count is astronomical, don't bother.Modern databases are very fast, especially for reading.  You should wait until you actually have the problem then measure to confirm you have the problem before you try to fix anything.If you run multiple read-only databases in parallel, you now have the maintenance problem of ensuring they are in fact identical.  Debugging the situation when they're not can be painful.