一切意味着继续开发针对sqllite，你可能很好，最初使用它。如果你发现你的应用程序有更多的用户下来轨道，你将要转换到postgres或MysqL。

sqllite的作者解决了这个on the website：

sqlite usually will work great as the database engine for low to medium traffic websites (which is to say,99.9% of all websites). The amount of web traffic that sqlite can handle depends,of course,on how heavily the website uses its database. Generally speaking,any site that gets fewer than 100K hits/day should work fine with sqlite. The 100K hits/day figure is a conservative estimate,not a hard upper bound. sqlite has been demonstrated to work with 10 times that amount of traffic.

sqlite will normally work fine as the database backend to a website. But if you website is so busy that you are thinking of splitting the database component off onto a separate machine,then you should definitely consider using an enterprise-class client/server database engine instead of sqlite.

所以我认为它的长短是，去为它，如果它不能很好地为你工作，使转换到企业级数据库是相当微不足道。然而，照顾你的模式，并设计数据库的成长和效率。

这里是a thread与一些更独立的评论围绕使用sqlite的生产Web应用程序。它听起来像已经使用一些混合的结果。

编辑(2014)：

因为这个答案发布，sqlite现在功能一个multi-threaded mode和write ahead logging mode，这可能会影响它的适合低中等交通网站的评价。

Charles Leifer写了a blog post关于sqlite的WAL(预写日志)功能和一些很好的考虑对适当的用例的意见。