A few people have asked about using sqlite on a server; obviously it's not a good choice if you have to write to the database.
What I am wondering about, is how well does it work in a read-only scenario? On the surface it seems it would work quite well: it supports concurrent access, and as long as we manage database updates in a smart way (restarts required...), it seems this is good.
In particular we are seeing really good performance, so this could be a big win.
Has anyone had bad experiences doing this? Any gotchas to watch out for? Anyone tried to scale this scenario in Java using sqlite4java?
Thanks, Eric