![]() ![]() ![]() ![]() Although the act of saving to database is quite quick, due to the sheer volume of users there would be problems!īy contrast, using PostgreSQL would let them have separate users writing at the same time. If Twitter was using SQLite, only one user could save a Tweet to a database at a time. These are written to a database for permanent storage. In Twitter, millions of users are constantly writing Tweets. This can make SQLite great at read-heavy applications, but not great at write-heavy applications or applications where many users should be able to write at the same time.įor example, Twitter. SQLite is very fast at reading from the database, but it is slow at writing (or rather, only one transaction can write to it at a time). In addition, for newer users PostgreSQL can be quite tricky to set up well. However, PostgreSQL is quite large in size and can require a lengthy setup. SQLite is extremely easy to set up and use. Don't assume that because a feature works in a certain way in SQLite, it'll work in the same way in PostgreSQL-no matter what the feature is!Īs well as the differences mentioned below (which are the main ones for us), this link contains basic descriptions of other differences: (opens new window) # Database size and setup Remember though that as you learn more about either one, that the other may not behave exactly the same way. In this chapter we'll talk about some of the differences between SQLite and PostgreSQL regarding the features we've already learned about. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |