Congratulations to the team! Happy to hear that you guys are going further. Looking forward to see what the future brings.
45 karma · joined December 11, 2014
@see: http://docs.mongodb.org/ecosystem/use-cases/product-catalog/
I personally miss Joins in MongoDB - but other vendors support Joins.
I don't want to create a schema in a relational database for that kind of use case. A MongoDB fits as well.
Edit: Sorry for my short and unprecise comment. I regret posting it, loosing all my Karma. Yes, of course I would use a schema, but I may use hundreds to get my products presented with all attributes and variants available. There is a set of attributes that will remain for all products, others will vary, some will change and will be dropped. Some may be conditional, depending on size or color. I could model that in RDBMS as well, adding those properties in an additional JSON or something else.
Yes, I'm also mainly using relational databases and just wanted to give an example of a use-case for MongoDB. I regret, sorry.
The way you solve things in document dbs like MongoDB is the key - not the fact that you get competitve performance in RDBMS as well.
I like Postgres and the possibility to easily use JSON data. But I still prefer to build applications the NoSQL way...