Ease of scaling mongodb vs mysql

Question

I am creating a Grails application, which is the backend for a mobile application. It is currently located on Amazon EC2. It saves data in mysql database. One instance is currently pointing to a database. I plan to deploy multiple application instances behind a load balancer and, ultimately, read requests go to subordinate db instances. We plan to release in the coming months and have a beta group of several thousand users. He is more intense than writing.

We have considered using mongodb instead of sql and consider it as a good solution.

Without much experience with mysql (or mongodb) scaling, it would be easier to scale mongodb as it has features such as automatic outline. (Looking for thoughts from people who did both). I think it’s now easier to switch to mongodb rather than being in “production” and forced to migrate.

Thoughts?

Answer 1

MongoDB has two versions of "scaling":

• Read scaling using replica sets .
• Set up scaling through sharding .

, . , EC2 ( ). , MongoDB , .

, ( ), , scalr, . , .

:

• - . - , .
• , , / . , MySQL, "", " ".
• 64- . MongoDB 64- . , , , 4 - 2-- ( , , , ).
• MongoDB - . , . , .

mongodb

"" . MongoDB , . , MySQL . , , .

, mongodb, 'production'

, .

?

. , , . EC2, . MongoDB , -. , :)