Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing SQLite vs MySQL with InnoDB, the Slant community recommends SQLite for most people. In the question“What are the best ACID-compliant scalable databases?” SQLite is ranked 2nd while MySQL with InnoDB is ranked 3rd. The most important reason people chose SQLite is:
SQLite is also only 350KiB in size.
Specs
Question Ranking
Pros
Pro Small
SQLite is also only 350KiB in size.
Pro Great language support
SQLite has bindings for a large number of programming languages, including BASIC, Delphi, C, C#, C++, Clipper//Harbour, Common Lisp, Curl, D, Free Pascal, Haskell, Java, JavaScript, Livecode, Lua, newLisp, Objective-C (on OS X and iOS), OCaml, Perl, PHP, Pike, PureBasic, Python, R, REALbasic, REBOL, Ruby, Scheme, Smalltalk, Tcl, Visual Basic.
Pro Self-contained
SQLite is largely self-contained. It requires very minimal support from external libraries or from the operating system.
Pro Portable
An SQLite database is a single ordinary disk file that can be located anywhere in the directory hierarchy. It works by sending requests to a single file where all the data is kept instead of communicating with a hosted database which gives access to an interface by making use of sockets and ports. The file format used is also cross-platform, so can easily be migrated to various machines.
This makes SQLite extremely portable throughout different applications, all that's needed to transfer the whole database is to make a copy of the file.
Pro Great for testing and first stages of development
Because of it's ability to scale and with the portability that a single-file database gives you without losing much of the power and features that SQL gives developers, it's a great choice for testing applications and for the early stages of development when the workload and the data that needs to be stored is not that large.
Pro Not unnecessarily fiddly
Pro Reliable
With less complication, there is less to go wrong.
Pro Zero configuration
There is literally no configuration required to get SQL lite up and running. This is mainly due to SQLite being serverless, there is no separate server process to install, setup, configure, initialize, manage, and troubleshoot.
Pro Multiple APIs
Some of these APIs include ODBC, Java (JDBC), Perl, Python, PHP, Ruby, and native C. Also, there are a number of third party APIs that are available for use to interact with the database
Pro Many applications available
There are a number of applications that are built with the focus of MySQL. Some of these include Drupal, Joomla, Wordpress and more.
Pro Scalable
Works well under simple operations or heavy tasks.
Pro Huge community support
Being the world's most popular open source database means there are tons of available examples and information for users' to access.
Cons
Con No multi user
Lacks multi-user capabilities, see SQLite vs. MySQL vs. PostgreSQL: A Comparison of Relational Databases.
Also see: Appropriate Uses For SQLite.
Con Some SQL features are missing
SQLite is made to be extremely lightweight and portable, but it still uses SQL. However, some SQL features such as RIGHT OUTER JOIN and FOR EACH STATEMENT are missing.
Con InnoDB is not fully configured
When you initially install MySQL, InnoDB needs to be configured to make it suite your needs and there are many issues you can come across.
Con Highly dependent on hard disk performance
