> a third company so that nobody inside the company knows that references were checked
That’s actually really interesting. If you are actively looking that prevents anyone in the company from knowing you are looking, even if they did a reference check. That might be because of some previous lawsuits around terminating someone while getting a reference check before actually getting a new job/leaving.
> However, it's only meant for local systems. Once you need to connect over a network or robustly handle simultaneous requests
That’s not really accurate any longer.
Mostly depends on how you layout your tables & files. If you shard the databases then multiple machines can act as writers for their shard. You can also split read requests from write requests and have read only machines scale up/down as much as you’d like. You can use multiple files in a query (there is a limit there).
So for example you can split the user table based on the first letter of the username and then depending on the rest of the database either a database file per user or per customer (organization). Of course more of everything is manual but it’s not as hard as you’d expect if you build for it.
At this point you're building your own networked database using sqlite just as a backing store. You should really reconsider if it's easier than using something designed for it.
If your entire system is sharded by username anyway for other reasons, then maybe what you've described works for you.
That’s actually really interesting. If you are actively looking that prevents anyone in the company from knowing you are looking, even if they did a reference check. That might be because of some previous lawsuits around terminating someone while getting a reference check before actually getting a new job/leaving.