We included SQLite alongside web and mobile applications where a small database was needed with minimum latency. Most commonly, this use case involved storing dynamic configuration values and user preferences.

SQLite is a great database solution when you have a small database that you need to package alongside an application, for example a database that stores user preferences. As it is local to the application, it bypasses issues you would have with other, larger database servers in terms of network latency. Its conformity (in the large part) to MySQL syntax and features make it easy to use as well.

While SQLite's lack of scaling features is forgivable (that wasn't what it was built for after all) some SQL features that are not implemented make it a hassle to write queries to SQLite databases in some instances.

On a Windows Forms app we used to query services thousand times for data that does not change so frequently. We also had to store some business information (imagine as storing a wizard progress) and that used to be handled using TXT files (and it was a mess). We changed to SQLite and it worked almost like a charm but as the app grew and we decided to create an architecture similar to Google Chrome (multiple processes) it became a major problem for all of them to both read and write at it (we had to create a proxy app to write).

Integrates nicely with .NET (specially Windows Forms) applications, it's really easy to use (specially if you're already familiar with SQL Server) and deployment is really easy (copy/paste required files).

It's locking architecture enables only a single process to write at a time so building a more complex application may cause hard-to-solve problems.

My overall experience using SQLite is good, but it is based on small projects, always working locally and with little information. If you are thinking of working on large-volume information projects, I recommend other applications related to somewhat better, more visual databases, and with more functions to generate code and store queries or procedures.

The best thing about SQLite is undoubtedly that you can work with it for free. In addition with SQLite we can perform any type of query that we would perform with another program.

What I like least about SQLite is undoubtedly nothing visual. The way to work with SQLite is through the console, and this may seem silly, and when you are accustomed it may not matter, but for people who begin to familiarize themselves with database environments, it is really useful for tables, and which is done with them, be fully visible. When displaying results by console, unless you print them in an external table, such as an Excel workbook, it will be quite complicated to see and analyze large results (Tables over 10k rows for example)

I love how SQLite is so portable, and can be used in different platforms. I doesn't need any bulky installation for me to use. It is so lightweight and there is no learning curve when you came from MS SQL.

Maybe when opening a large sqlite file around 1GB above, it hangs up and sometimes fails to load. But maybe that's my fault because SQLite is not intended for storing large data. Good product anyway.

We have used SQLite in developing many mobile apps, mostly Android App and as a database at back end we integrated this light weight DB system. The processing speed of queries is exceptionally fast. All the databases are working well.

SQLite is object based relational query language which keeps and maintained the whole databases in a very light weight, usually within 500kb to 1mb size, depending on size of databases. This database system has everything which a standard databases must have like relationships, events, all operations, etc. SQLite is very helpful in building application for Mobiles which stores databases in locally.

1. No dedicated server required. 2. Very light weight and easy to follow commands with knowledge. 3. Large community support makes learning this language even more fast and easy 4. Easy to keep backups as the whole database stored in single file. 5. Easy to implement and integrate.