4 ms·
To be fair, both MongoDB and Elasticsearch have had serious issues as pointed out via the Jepsen tests. https://aphyr.com/posts/317-jepsen-elasticsearch https:
by d4l3k 8y ago
To be fair, both MongoDB and Elasticsearch have had serious issues as pointed out via the Jepsen tests.
https://aphyr.com/posts/317-jepsen-elasticsearch https://aphyr.com/posts/317-jepsen-elasticsearch
https://aphyr.com/posts/323-jepsen-elasticsearch-1-5-0 https://aphyr.com/posts/323-jepsen-elasticsearch-1-5-0
Though, all those issues have been fixed for both MongoDB and Elasticsearch so it's not necessarily fair to judge them based off past performance.
https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html https://www.elastic.co/guide/en/elasticsearch/resiliency/cur...
https://www.mongodb.com/mongodb-3.4-passes-jepsen-test https://www.mongodb.com/mongodb-3.4-passes-jepsen-test
- xaranke 8y agoThe results for ElasticSearch are from 2015, curious to see how relevant they are now especially given that the team has been working on addressing these issues in the interim.
- tschellenbach 8y agoAlso elastic back then was used as a place where you copy your data, not your main data store. (Their positioning changed later) MongoDB was supposed to be used for your primary data store.
- Fiahil 8y agoThese jepsen tests cover elasticsearch 1.5, a large number of issues have been progressively fixed. We're now at ES 6
- Thaxll 8y agoThose Jepsen are not that useful, I can point to you Postgres issues where it would corrupt the DB, does it means you shoudn't use Postgres?
- baq 8y agoThey're very useful - these posts compare actual functionality with the project's documentation.