![]() ![]() The blog example shows up so much for DBMS like MongoDB, because it showcases what NoSQL / document storage is very scalable and performant in: mostly isolated documents with a few views / ways to order them and filter them. The main thing to consider around database choice, is what "shape" the data will be in, and the kind of read/write patterns you expect of that data. I can't speak for the NestJS vs ExpressJS discussion, but I can given a viewpoint on databases. I suspect that putting in a little bit more work up front will pay high dividends and productivity once the data is normalized.Īgain - it's largely a matter of preference but I prefer SQL almost every time. I'm sure you can imagine what the data sets would look like if you use MongoDB or Postgres. It sounds like the type of problem you need to reverse engineer. I'm using Firestore with one of my apps and MongoDB with another app but they both use MySQL for the heavy lifting and then a document database for things like permissions, caching, etc. ![]() I'm much more experienced with MySQL than any other database and I am having a hard time getting on board with noSQL entirely because it's really hard to query complex data with relationships using noSQL. You're going to have a really hard time normalizing the data when you can't manipulate relationships and bulk edit with a nice update query. I see that someone else responded and recommended MongoDB but since you are doing data analytics, I highly recommend you go with SQL. We do not need to define schema first.This is largely a matter of opinion. Data of any structure can be accessed and stored easily and quicklyģ. Support is available in the free version, but you will need to pay for it.ģ. You might have to spend a lot of time and effort to get MySQL to do the things that other systems can do automatically, e.g. It can be used to work with other databases, including DB2 and Oracle.ġ. It offers a lot of functionality even for a free database engine.ģ. Pros and Cons of MongoDB and MySQL : MySQLĢ. And if you need to handle a large volume of data then MongoDB will help you. MongoDB : if your data is unstructured and complex, or if you can not pre-define your schema, you have better option for MongoDB. MySQL : If your data is structured and simple, Or if you can define your schema, if smaller volume of data then you can use MySQL. you should take care about your project requirements. MySQL and MongoDB both have their weaknesses and strengths.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |