If you are expecting to have 10 simultaneous access writing at the database at a time SQLite may perform well, but you won't want an 100 user application that constant writes and reads data to the database using SQLite. SQLite is made for simplicity and Self Contained Database Applications. "LOCK THE WHOLE TABLE AND EXECUTE A SINGLE QUERY EACH TIME"
This will make a single user connection slower, but pays off in the future, when 100's of users are online, and in this case, the simple MySQL for example, even with a single user will create an access QUEUE, lock tables partially instead of allowing only single user-per time executions, and other pretty complex tasks in order to make sure the database is still accessible for any other simultaneous access. RDBMS's Makes a lot of extra work that make them more Scalable
#SQLITE VS MYSQL JAVA UPDATE#
For example, SQLite will lock the whole table if an update is going on, and queue the orders. The way servers handle multiple requests is completely different and way more complex and optimized for high concurrency. SQLite uses a very simplistic access algorithm, its fast but does not handle concurrency.Īs the database starts to grow, and the amount of simultaneous access it will start to suffer. The access time for SQLite will appear faster at first instance, but this is with a small number of users online. At First Access Time will Appear Faster in SQLite
0 kommentar(er)
