I've deployed SQLite to a large number of production software, from embedded systems to web servers handling thousands of daily vistors. In fact, SQLite is my tool of choice when it comes to a small/medium relational-db-based web project.
Sqlite is not a toy db. It is an impressive piece of software engineering.
So, unless you have a very narrow definition of the word production, you should do read up on SQLite (the official website is excellent) and seriously consider it for your next project.
SQLite should absolutely be used in production, where it makes sense. The one area where sqlite has a big disadvantage is concurrent writes. If you have read-only data, cached data, etc. then sqlite can happily be used in a high traffic production system, with millions of rows and many GB of data. It's also a good store for configuration data, or something like an admin backend. The portability of sqlite database files is a really nice feature.
I've deployed SQLite to a large number of production software, from embedded systems to web servers handling thousands of daily vistors. In fact, SQLite is my tool of choice when it comes to a small/medium relational-db-based web project.
Sqlite is not a toy db. It is an impressive piece of software engineering.
So, unless you have a very narrow definition of the word production, you should do read up on SQLite (the official website is excellent) and seriously consider it for your next project.