Need advice about which tool to choose?Ask the StackShare community!
CouchDB vs Event Store: What are the differences?
Developers describe CouchDB as "HTTP + JSON document database with Map Reduce views and peer-based replication". Apache CouchDB is a database that uses JSON for documents, JavaScript for MapReduce indexes, and regular HTTP for its API. CouchDB is a database that completely embraces the web. Store your data with JSON documents. Access your documents and query your indexes with your web browser, via HTTP. Index, combine, and transform your documents with JavaScript. On the other hand, Event Store is detailed as "*The open-source, functional database with Complex Event Processing *". It stores your data as a series of immutable events over time, making it easy to build event-sourced applications. It can run as a cluster of nodes containing the same data, which remains available for writes provided at least half the nodes are alive and connected.
CouchDB and Event Store belong to "Databases" category of the tech stack.
CouchDB is an open source tool with 4.26K GitHub stars and 844 GitHub forks. Here's a link to CouchDB's open source repository on GitHub.
According to the StackShare community, CouchDB has a broader approval, being mentioned in 76 company stacks & 196 developers stacks; compared to Event Store, which is listed in 9 company stacks and 11 developer stacks.
We implemented our first large scale EPR application from naologic.com using CouchDB .
Very fast, replication works great, doesn't consume much RAM, queries are blazing fast but we found a problem: the queries were very hard to write, it took a long time to figure out the API, we had to go and write our own @nodejs library to make it work properly.
It lost most of its support. Since then, we migrated to Couchbase and the learning curve was steep but all worth it. Memcached indexing out of the box, full text search works great.
Pros of CouchDB
- JSON43
- Open source30
- Highly available18
- Partition tolerant12
- Eventual consistency11
- Sync7
- REST API5
- Attachments mechanism to docs4
- Multi master replication4
- Changes feed3
- REST interface1
- js- and erlang-views1
Pros of Event Store
- Trail Log1