11/18/2023 0 Comments Sqlite transaction performance![]() ![]() There are three main metrics on which we might want a database to be able to scale: the total amount of data it can store, the read throughput, and the write throughput. We'll look at scalability, performance, availability, operational complexity, and a few other things. I won't be comparing to more "cloudy" solutions (that'll be the subject of another post), but I think it's still useful to consider this sort of thing even if you end up using some sort of IaaS product. In this post, I'll compare a typical " multitier architecture" with a web server and separate database server (postgres, etc) to running that same app all on a single machine using SQLite. However, due to improvements in SQLite, hardware performance, and third-party libraries over the past ~decade, it now makes a lot of sense to use SQLite for many web projects. Historically, use of SQLite has usually been constrained to user programs (like browsers or apps), rather than servers. SQLite is a incredibly popular database - you likely have dozens or hundreds of SQLite database on whatever device you're reading this on, regardless of whether that's a smartphone or a tablet, and regardless of what manufacturer or browser it is. ![]() Today I want you to consider: what if SQLite would do just fine?įor those who are unfamiliar, SQLite is a implementation of SQL as a library - this means that rather than running a SQL server that you program talks to, you embed the SQL implementation directly in your program, and it uses a single file on disk as a backing store. If you were creating a web app from scratch today, what database would you use? Probably the most frequent answer I see to this is Postgres, although there are a wide range of common answers: MySQL, MariaDB, Microsoft SQL Server, MongoDB, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |