11/20/2023 0 Comments Pros and cons sqlite vs postgresql![]() ![]() ![]() I don't want to officially recommend another tool, but you should really checkout prisma, firebase, amplify, or Azure App Services for this app! Just go completely backend-less ![]() Whereas mongoDB Atlas has some great free-tier options.Īlthough your data might be easier to model in Postgres, you can certainly model your data as a single list of items that have a category attached. It provides 20MB for free with 5 concurrent connections, you should be okay to manage these limitations if you decide to go Postgres in the end. Hosting SQL databases for production is not cheap! the cheapest solution I know of for Postgres is ElephantSQL. your app is pretty simple in concept, SQL databases will add unnecessary complexity to your system, either through ORMs or SQL queries. I think Postgres is wrong for the following reasons:ġ. you absolutely need a database that is shared by all users of your app, therefor IndexedDB is out of the question.ģ. I think Mongo is going to be what you're looking for on the following basis:ġ. Your app is essentially a list of objects that can belong to a categoryģ. You're looking to have a relatively high-read with a lower write volumeĢ. It also sounds like your app can grow in a linear capacity based on the number of users, and the amount of data, which is the perfect use-case for noSQL databases (linear, predictable scaling).Ĭorrect me if I have any of these assumptions wrong.ġ. I think your best and cheapest choice is going to be MongoDB, Although Postgres is probably going to be the more scaleable approach, you likely have a good idea of how you want to present your data, and the app seems small enough that you shouldn't need to worry about scaling issues. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |