SQLite is a C library that implements an embeddable SQL database directly into the application. Programs that use the SQLite library can have access to SQL database without running a separate RDBMS process.


Contrary to what one might think, SQLite is not a client library used to connect to a big database server, it is the server itself. The SQLite library reads and writes directly to the database file, storing in the same application server. The use of SQLite is recommended once simplicity of administration, implementation and maintenance excel countless resources, relevant only to great applications and more complex demands. Applications that do not have such requirements are very common, thus the final price of the project in these cases is reduced and this turns out to be a key differentiator in using SQLite. A detailed analysis can determine the use of this option.

Examples of most common use of SQLite are sites with less than one hundred thousand requests per day, embedded devices and systems, desktop applications, statistics and analysis tools, database learning and implementation of new SQL extensions.

Not recommended for SQLite use are the websites with a large volume of access, large amounts of data (more than 10GB), systems with great competition and client/server applications.

Some features of SQLite:

  • Software livre/domínio público e Multiplataforma;
  • Mecanismo de armazenamento seguro com transações ACID;
  • Não necessita de instalação, configuração ou administração;
  • Implementa a maioria do SQL92;
  • O Banco de Dados é guardado em um único arquivo;
  • Suporta bases de dados acima de 2 terabytes;
  • Sem dependências externas.

• Free Software/public domain and Multiplatform;

• Secure storage mechanism with ACID transactions;

• Requires no installation, configuration or administration;

• Implements most of SQL92;

• The database is stored in a single file;

• Supports databases up to 2 terabytes;

• No external dependencies.


The simplicity in using SQLite, however, does not exempt the user basic care, particularly regarding its installation. Therefore, some important precautions must be taken:

• The database files should not be placed in visible directories on the web – i.e., below the public_html folder.

• If you need to put it in this structure, the directory with .htaccess must be protected;

• Tables should have little data as the SQLite runs on the same server as the site (as opposed to MySQL and SQL Server running on separate servers). This can compromise application performance in general, if it gets too large or has multiple simultaneous accesses;

• For the name of the files, it is important to use suffixes like “.db”, “.sqlite” so that it is easy to recognize the database file.

You might also like…

How to implement A2F using Own Development in NodeJS in a Scriptcase application

A2F using Own Development in NodeJS A2F: In a previous article, we talked about Swivel as an extern...

Specialists or generalists, who gets a better advantage by using Scriptcase?

Hey there! Today  we will figure what are the ideal profiles for those who wish to take advantage o...

Disabling autofill and autocomplete Chrome browser in login screens

Hello, here I want to show an alternative to disable the autofill and autocomplete of the chrome bro...

Comment this post

Get new posts, resources, offers and more each week.

We will use the information you provide to update you about our Newsletter and Special Offers. You can unsubscribe any time you want by clinck in a link in the footer of any email you receive from us, or by contacting us at sales@scriptcase.net. Learn more about our Privacy Police.