3 ms·
Can you explain a bit why ES isn't a good solution for storing data itself? I inherited a legacy Mongo solution, and all the data is duplicated and indexed in
by hiram112 7y ago
Can you explain a bit why ES isn't a good solution for storing data itself?
I inherited a legacy Mongo solution, and all the data is duplicated and indexed in ES, so I've always wondered why we're using both. Mongo has none of the SQL capabilities that would make my life easier, and the types of queries allowed by Mongo could be done with ES.
What are the negatives of ES alone?
- manigandham 7y agoIt's not reliable: https://www.quora.com/Why-shouldnt-I-use-ElasticSearch-as-my-primary-datastore/answer/Mani-Gandham https://www.quora.com/Why-shouldnt-I-use-ElasticSearch-as-my... The v7 upgrade to a new cluster protocol (zen2) has improved things but overall the system has a long history of losing or destroying data. It's better to have a primary OLTP system that's ACID and reliable while using ES as the secondary search source. You can also remove the _source field if you just need matches without the original content. It's common to see pattern used with a relational database since, as you can see, Mongo doesn't buy you much else as another document-store.
- manigandham 7y agoFollow up: MongoDB is adding full-text search capabilities: https://www.youtube.com/watch?v=4QUGWnz-XaA https://www.youtube.com/watch?v=4QUGWnz-XaA
- hiram112 7y agoThank you very much. It seemed like we were just duplicating a bunch of scheme-less json for no reason, but if ES can lose data, that's probably not a good idea.