Perfect database tool for embedded software

I work a lot with SQLite as it is the primary medium of local storage in Android devices (and by extension, Android applications) which I work with on a daily basis, and SQLite is just perfect for the purpose it serves on these devices. It's lightweight so you don't have to worry most times about how much of the user's storage space your database is going to take up. There's not much difference between the standard SQL commands and those used in SQLite, and many have reported that SQLite is a good starting and training resource for SQL in general.

Pros

Doesn't need a separate server. Lightweight and portable. Integrates most of the commands, functions and syntax of other SQL software. Optimized for use on devices that need to store data locally. Large user base and community (support).

Cons

All operations are locked to a single process, so it's not suitable for large scale database operations (which is not what you should be doing locally on a device anyway).

Nice for small solutions

Pretty good for quick tests and development experiments, especially when you like SQL, not great for large production-grade datasets.

Pros

It is serverless, needs no configuration, easy to start working with and use in development, especially when fixing/improving some legacy software. When used correctly, especially with limited amount of data, allows for fast queries.

Cons

It is not built for large-scale applications. Another thing is that it is not easy to predict performance for queries on large amounts of data, even if the user knows how that database is built. It is sometimes easier to design your own (customized) data structure rather than using the standard product.

SQLite - compatability at it's best level

SQLite has become more and more popular among the users because of its easy installation and easy accessing . As it is compatible with most of the programming languages and its light weight it is more popular among mobile application developers

Pros

SQLite is a light weighted data base which could be embedded with any software. Due to the light weightage of the product the data base is more popular In mobile application development. With it’s light weight it is also fast. SQLite is almost 35% faster than any other file system. SQLite is easy to use and there is not special installation or configurations needed to be done in order to use the product. All user have to do is download the libraries and run them in the computer. It is compatible which is why the product can be used with many programming languages with out any issues. Users are given a chance to extend their data base in future by adding new tables or new columns to the existing tables which is a great help for the ongoing projects.

Cons

SQLite is not a multi-user platform where the users can handle concurrent writes. There for SQLite is not good for intensive applications with rapid data logging. If the system has concurrent transactions where lot of users keep accessing the same set of data simultaneously then SQLite is not a good choice for the project. SQLite data bases are restricted to maximum of 2GB in most of the cases.

Experience with SQLite

Describe your general experience with SQLite It is very useful for me to be able to store information and consume it from different sources without having to implement specific software to do so. Its portability capacity has allowed us to distribute work effectively.

Pros

The few resources you need and its portability. This allows us to use the stored data from any medium.

Cons

That there is no native way to make it multi-user. That there is no native way to merge files from the same database, when they have been modified by different users and platforms.

The best solution for small, pre-packaged databases

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.

Pros

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.

Cons

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.