is an ACID-compliant relational database management system, contained in a relatively small library written in C
SQLite is a lightweight relational database engine. accessible through the SQL language. Unlike traditional database servers like MySQL or PostgreSQL, its particularity is not to reproduce the usual client-server scheme, but integrated directly into the programs.
SQLite is a complete single-file relational database management system. SQL, or Structured Query Language, is the industry standard programming language for storing and retrieving data. Popular SQL database managers include Oracle, IBM's DB2, Microsoft's SQL Server and Access, as well as free MySQL and PostgreSQL software.
Recently the founder of the project complained that "SQLite is explicitly and unambiguously 'open source, not open contribution'", It mentions that the project currently has a limited objective, which is to be a fast, small and reliable integrated database.
The reason for This comment stems from two things, the first of them that he and his team argue SQLite needs to be improved with essential new features. These include in particular:
- Support for distributed databases available on multiple servers
- Asynchronous I/O support via the new Linux io_uring API
- eBPF to optimize SQLite by allowing certain operations to run in the kernel
- Support for user-defined functions in Wasm (WebAssembly) to allow the use of other languages, which are compiled into Wasm, instead of C.
- The libSQL project plans to use Rust in conjunction with C to implement these changes.
The second is that recentlye has created a new fork of SQLite, called libSQL, aims to modernize the hugely popular embedded SQLite DBMS. Besides that he plans to use Rust together with C to implement the changes that the founder argues.
As such, many might mention why a fork and not make proposals to the SQLite project itself? and as already mentioned, problem is that the SQLite project has a limited goal
According to the SQLite development team, the DBMS is probably one of the five most widely implemented software modules of any description. Given that SQLite is widely used on all smartphones and there are more than 4000 billion smartphones in use, each containing hundreds of SQLite database files, it is likely that there are more than 4000 billion smartphones in use. use and a billion SQLite databases in use.
Thanks to its extreme lightness, SQLite is one of the most widely used database engines in the world. It is used in many consumer programs and is also very popular in embedded systems, including most modern smartphones.
Size isn't everything to the humble creator of SQLite, as Apparently he has the idea of turning the project into something profitable, since as such he does not receive royalties for the millions of copies used by commercial and non-commercial users and on the case, he mentions that he is not really interested in the monetary part and in tending to his argument, his annoyance goes towards another approach.
This is an unusual approach, even in the free software world. Most open source code is licensed under an agreement such as the GNU GPL (General Public License), which includes terms that ensure the software remains free, although today several developers of important projects have reached a conclusion, where they do not entirely disagree that their products did not receive support from commercial users (something similar to what QT arrived at).
“I went through all the licenses,” says Hipp, “and thought, why not just put it in the public domain? Why put these restrictions on it? I never expected to earn a dime. I just wanted to make it available to other people to solve their problem. »
"We're not trying to compete with those other engines," says Hipp. “Our goal is not to add all kinds of bells and whistles, but to keep SQLite small and fast. We set an arbitrary limit to keep the library space below 250KB.”
Finally, Glauber Costa mentions that «the success of SQLite combined with its relatively closed development makes it difficult for a fork to succeed, another option is to wrap SQLite with additional functionality, but this has limitations”, to which Costa alludes.
Source: https://devclass.com/