Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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.