3 ms·

So... - Lack of Transactions - No joins - Schema-less If these are important, you really shouldn't have been using schema-less document database. - Unstabl

So... - Lack of Transactions - No joins - Schema-less If these are important, you really shouldn't have been using schema-less document database. - Unstable This is the only real point I can give to you unless you were actually running the bleed edge version. If you were using the trunk/head version you were just asking for the problems you were having.

bad_user 16y ago
> If these are important, you really shouldn't have been using schema-less document database. What does that have to do with his complaints? The "lack of transactions" is a lack of MVCC. This has nothing to do with NoSQL, RDBMSs, document databases, or schemas. Many NoSQL databases do offer some transactions support ... like CouchDB or the storage in Google's AppEngine. "No joins" ... we've been taught for years the virtues of normalization / relational data, both in school and throughout the industry, and now we should let go of everything we've been taught. Great, but where are the best practices / patterns? Where are the books on data-modelling? "Schema-less" ... it's not really schema-less, it's just that the schema is defined at the application layer. Again, where are the best practices for that? One advantage of MongoDB in combination with something like Rails is said to be the lack of migrations ... I view that as a disadvantage as migrations are a great way of documenting what's changed. To get back to my point ... don't shout at potential users something akin to RTFM ... educate them instead.
- dschobel 16y ago
  It isn't RTFM as much as do some research before choosing your data store. The majority of his enumerated gripes aren't unexpected or hidden attributes of mongodb but fundamental considerations when deciding on a data store.
  - epochwolf 16y ago
    And his data loss issues seem to be related to server reboots according to one of his later comments. MongoDB's docs clearly state that the database must be shut down safely or data loss will happen. (MySQL is the same way, it gets really annoyed at hard reboots)

bad_user 16y ago

> If these are important, you really shouldn't have been using schema-less document database. What does that have to do with his complaints? The "lack of transactions" is a lack of MVCC. This has nothing to do with NoSQL, RDBMSs, document databases, or schemas. Many NoSQL databases do offer some transactions support ... like CouchDB or the storage in Google's AppEngine. "No joins" ... we've been taught for years the virtues of normalization / relational data, both in school and throughout the industry, and now we should let go of everything we've been taught. Great, but where are the best practices / patterns? Where are the books on data-modelling? "Schema-less" ... it's not really schema-less, it's just that the schema is defined at the application layer. Again, where are the best practices for that? One advantage of MongoDB in combination with something like Rails is said to be the lack of migrations ... I view that as a disadvantage as migrations are a great way of documenting what's changed. To get back to my point ... don't shout at potential users something akin to RTFM ... educate them instead.

dschobel 16y ago
It isn't RTFM as much as do some research before choosing your data store. The majority of his enumerated gripes aren't unexpected or hidden attributes of mongodb but fundamental considerations when deciding on a data store.
- epochwolf 16y ago
  And his data loss issues seem to be related to server reboots according to one of his later comments. MongoDB's docs clearly state that the database must be shut down safely or data loss will happen. (MySQL is the same way, it gets really annoyed at hard reboots)