Migrating a large site from SQL Server to MongoDB - Lessons Learned
SQL and NoSQL are different tools for different jobs. A couple of months ago we migrated a large site from SQL Server to MongoDB, it was a bumpy road and I decided to write this article to share what we learned:
http://www.wireclub.com/development/TqnkQwQ8CxUYTVT90/read
12 comments
[ 3.4 ms ] story [ 36.5 ms ] threadI'm not sure if there's ever a good reason to use {fsync: true} vs {j: true}
I think given that one of the parameters is called "fsync" using "fsync" should mean that.
Why would you conclude that MongoDB was "fast" and SQL Server was slow? Did you run SQL server on the same SSD's and multiple HDD's?
to willvarfar's comments, what was the real fsync cost and didn't you get ACID with SQL Server? Now, if ACID is not really required, and you really really need flexible schemas, then by all means ... I understand that you want distributed-queryable-notepad, not a relational database!