If you need a document-based approach there are a few options you might want to consider (and certainly not table-based relational db). I've migrated part of o

If you need a document-based approach there are a few options you might want to consider (and certainly not table-based relational db). I've migrated part of our project to Couchbase (not CouchDB or others) and beside a technical comparison... I've appreciated the ease of onboarding for new hires to this technology, scalability and maintainability... all aspects that become critical in the long run. If your project involves mobile clients, I'm sure your devs will appreciate the easy to use SDKs packaged with features (I personally loved the fine grained offline sync with backend and/or between two local DBs) A technical comparison is here, but it's on the couchbase site so it could be biased https://www.couchbase.com/comparing-couchbase-vs-mongodb https://www.couchbase.com/comparing-couchbase-vs-mongodb