If you're building a small web service, SQLite3 will do fine. If you want to scale big you might be able to use SQLite3 for some pieces of it, but you can't scale up a web service to thousands of servers with tens of cores and one single SQLite3 DB -- that just doesn't work given SQLite3's architecture. The good news is that in web services you're constantly rewriting the service, and so you'll have an opportunity to move to a different solution at the right time, and if using SQLite3 gets you off the ground quickly, then so much the better for you.
On the other hand, you might want to consider horizontal scaling from day one, in which case you really need to look at databases that support horizontal scaling. There are quite a few. Most cloud vendors offer such services and software, for example. For example, there's Apache's Cassandra, Amazon's DynamoDB, there are NoSQL-type databases, ... Use the right tools for your problem. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
