I have searched the monastery to glean all the wisdom I could in regard to using SQLite--nearly all of which is several years old. It appears that SQLite has matured over the last few years, and that concurrency has improved.
I am developing a small CGI::Application that will be deployed into a shared hosting environment at dreamhost. The app uses DBIx::Class for ORM, and has only about 10 tables. I am expecting no more than a dozen concurrent users, but scalability may become an issue.
What insight can you offer in regard to using SQLite3 in a light production environment?
I have MySQL available in both development and production environments, so is it worth even considering SQLite3?
Thanks, AkoyaIn reply to SQLite3 use in production by Akoya
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |