4 ms·
Agreed to an extent. It does have its' place and is definitely very easy to use if you have a limited number of collections, mostly distinct in use and have de
by tracker1 8y ago
Agreed to an extent. It does have its' place and is definitely very easy to use if you have a limited number of collections, mostly distinct in use and have deeply structured objects.
The ease of clustering is pretty nice for either replica sets or basic sharding, but sharding + redundancy isn't great, and if you happen to have a majority of nodes offline it may never catch/sync up right again which may require bringing on/off new nodes or the whole thing down and restoring from backup.
About 4-5 years ago when a bulk of Azure went down, I experienced this, and it wasn't fun to say the least. Fortunately it was mainly a replica of primary data source for search/display for mostly-read scenarios and was easier to re-replicate the records from SQL in the end. If I were to do it again, I'd probably reach for Elastic first.
It can be very good for some use cases and less than good for others. The clustering is absolutely easier than anything but RethinkDB (in the box) and SQL Server (break out your checkbook) in my opinion.