SQLite What ?
Actually, as the name suggests sqlite , sql and lite the expression of a lightweight sql engine solution evokes my ear.If we think in detail, there is still no big difference.
So what’s the difference from other sql engines? What are the reasons for it to take an advantageous position over others? Before i say this, let’s take a look at other database types as a category.
Most generally categorized by type
- Relational databases
- NoSQL databases
- Graph Databases
I divide it into 3 main categories.. This is not a generally accepted separation method. Category types can be increased. like ER model, like OOP etc..
Which category does SQLite belong to? It belongs to Relational Database category. Just MySQL, PostgreSQL, MSSQL, Oracle Database, MariaDB .. Is that all? Of course, that’s not all.SQLite is in the same category as these, so is doing the same thing with them? Theoretically yes there is a little difference in practice. I have to separate another sub-break into itself. This is also serverless. Yes our keyword is serverless.
So what do I mean? I add description of the SQLite organization here. It is much more clearly explained.
“Most SQL database engines are implemented as a separate server process. Programs that want to access the database communicate with the server using some kind of interprocess communication (typically TCP/IP) to send requests to the server and to receive back results. SQLite does not work this way. With SQLite, the process that wants to access the database reads and writes directly from the database files on disk. There is no intermediary server process.”
Well I think we now have an idea of what it is.
What is for ? Usage Cases
But of course this does not mean that I use it in every project to provide the best performance.I think it is appropriate to use for standalone applications, Cache mechanisms and experimental projects.For example, python can be a good choice for quick results in a project that will work standalone.
