I have worked with MySQL more than MongoDB, but from what I've learned from MongoDB it's just what I needed, but it also has it's limitations that MySQL can do (for instance auto increment)
Would it be smart to use MongoDB for everything, and use MySQL for only certain things?
For instance use MongoDB to store users and everything else, but use MySQL to make for example a ticket system.
It sounds perfectly reasonable to use two database technologies in one project. Just make sure you use the right tool for the job.
It's common to use MySQL as the primary storage and MongoDB as caching/intermediate storage for speed.
You can for example have read-intensive data in MongoDB. The data for generating reports is perfect for a relational system like MySQL.
There is a pretty good discussion of Use Cases for MongoDB on the main MongoDB site . In general, if your business case includes the need for transactions and heavy T-SQL functionality, then you'd be better served by using a RDBMS such as MySQL.
Good Use Cases for MongoDB are as follows:
Here is a well-typed discussion of mongodb usage, by someone who took mongoDb courses
Considerations for choosing or not choosing MongoDB
The blogger mainly says that using mongodb with other DB systems is perfectly fine , yet using it system wide , can be most challenging and almost impossible at some certain scenarios.
Here are some subtitles :
Reasons to choose Mongo
Reasons not to choose Mongo
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.