4 ms·
We have highly relational data How did your project end up selecting MongoDB? That seems like exactly the sort of thing that it's not good for. (I'm not just
by tjr 13y ago
We have highly relational data
How did your project end up selecting MongoDB? That seems like exactly the sort of thing that it's not good for.
(I'm not just being rhetorical; were there other attributes of MongoDB that made it seem preferable to a relational database earlier in the project?)
- woah 13y agoWhen you really start looking into it, what projects actually are good for Mongo? EDIT: It's nice and quick for prototypes. Ironically, I'm building one with it now.
- boomzilla 13y agoAfter a few months dealing with a system that's built on Mongo ad the data store, I've come to the conclusion that MongoDB only use cases are: 1. A persistent cache, or a compute-ahead read-only data store. 2. A write-only store for high volume but non-critical data, such as comments, log events, etc. MongoDB should never be the primary source of truth data store. Nothing can replace a relational DB for that purpose, yet.
- vinceguidry 13y ago> 1. A persistent cache, or a compute-ahead read-only data store. Even then, you're probably better off with Redis or memcached. > 2. A write-only store for high volume but non-critical data, such as comments, log events, etc. Just write to disk. It's very hard to beat flat file text for this use case and most of the time it's not worth it.
- bsg75 13y ago> compute-ahead read-only data store Definition? As in pre-aggregated data, i.e. materialized views or summary tables?
- themckman 13y agoIt was simply a matter of joining the project after the decision had been made, unfortunately.
- andrewflnr 13y agoOK, but how did they decide on Mongo before you got there?