Which Database is Good?


Author
Message
Arjun Kumar
Arjun Kumar
Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)
Group: Forum Members
Posts: 2, Visits: 0
Hello Everyone, I am just join this community to clear my doubt. I am currently using Mysql version 5.7 and I am a little bit confused between Mysql and MongoDB. I am thinking to switch on MongoDB. Can anyone tell me which database is good to use?
DOUBT
rohanjoshi0894
r
Attaching to Tangle (1 reputation)Attaching to Tangle (1 reputation)Attaching to Tangle (1 reputation)Attaching to Tangle (1 reputation)Attaching to Tangle (1 reputation)Attaching to Tangle (1 reputation)Attaching to Tangle (1 reputation)Attaching to Tangle (1 reputation)Attaching to Tangle (1 reputation)
Group: Forum Members
Posts: 1, Visits: 0
MySQL is a relational database management system (RDBMS) that stores data in tables and uses structured query language (SQL) for database access. In MySQL, you pre-define your database schema based on your requirements and set up rules to govern the relationships between fields in your tables.

If your data structure fits nicely into tables and rows, MySQL will offer you robust and easy interaction with your data. If it's the performance that is your concern, there is a good chance you don't really need MongoDB. Most likely, you just need to index your data properly. If you require SQL or transactions, you'll have to stick with MySQL.

MongoDB stores data in JSON-like documents that can vary in structure. Related information is stored together for fast query access through the MongoDB query language. MongoDB uses dynamic schemas, meaning that you can create records without first defining the structure, such as the fields or the types of their values. You can change the structure of records (which we call documents) simply by adding new fields or deleting existing ones.

If your data seems complex to model in a relational database system, or if you find yourself de-normalizing your database schema you should consider using MongoDB. If you find yourself trying to store serialized arrays or JSON objects, that's a good sign that you are better off MongoDB. If you can't pre-define your schema or you want to store records in the same collection that have different fields, that's another good reason.

Read More.
Edited 3 Months Ago by rohanjoshi0894
Arjun Kumar
Arjun Kumar
Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)Attaching to Tangle (46 reputation)
Group: Forum Members
Posts: 2, Visits: 0
rohanjoshi0894 - 26 Sep 2019
MySQL is a relational database management system (RDBMS) that stores data in tables and uses structured query language (SQL) for database access. In MySQL, you pre-define your database schema based on your requirements and set up rules to govern the relationships between fields in your tables.

If your data structure fits nicely into tables and rows, MySQL will offer you robust and easy interaction with your data. If it's the performance that is your concern, there is a good chance you don't really need MongoDB. Most likely, you just need to index your data properly. If you require SQL or transactions, you'll have to stick with MySQL.

MongoDB stores data in JSON-like documents that can vary in structure. Related information is stored together for fast query access through the MongoDB query language. MongoDB uses dynamic schemas, meaning that you can create records without first defining the structure, such as the fields or the types of their values. You can change the structure of records (which we call documents) simply by adding new fields or deleting existing ones.

If your data seems complex to model in a relational database system, or if you find yourself de-normalizing your database schema you should consider using MongoDB. If you find yourself trying to store serialized arrays or JSON objects, that's a good sign that you are better off MongoDB. If you can't pre-define your schema or you want to store records in the same collection that have different fields, that's another good reason.

Read More.

Thanks @rohanjoshi0894 for giving great information.
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search