3 ms·
The relational data model is not perfect for every use case. I use Cassandra for high volume, time series data, MongoDB for documents, Titan/Neo4J for graph dat
by threeseed 12y ago
The relational data model is not perfect for every use case. I use Cassandra for high volume, time series data, MongoDB for documents, Titan/Neo4J for graph data, ElasticSearch when I need better indexing. I pick a different technology depending on what I think works best for the use case.
At no point have I thought so condescendingly as you do that MY choices are the best for everyone. They aren't. And I promise you that picking the one technology/approach for everything doesn't work anymore. It's a heterogeneous world out there.
And that link you posted is pathetic. MongoDB is not suited for social network style data neither is many other databases. Doesn't mean they are useless for every use case.
- aikah 12y agoare you really juggling with 3 dbs in the same project?
- chris_wot 12y agoLook, I know I'm being negative on MongoDB. But I really wanted it to be awesome, but it's inherent limitations are just so start that I feel that most people who use it are doing so because they are misinformed or misled. If you have found success with it, that's great. I just have very strong reservations about the entire data model for most people. Ease up there buddy! I wasn't being condescending. I just think that for most people a relational model is probably what they are looking for. I don't think the article I posted is "pathetic", as that's a bit condescending... Just showing one datapoint that shows where people think they need a hierarchical data model, in fact they need an relational model.