Event Store vs RethinkDB: What are the differences?
Event Store: 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; *RethinkDB:** JSON. Scales to multiple machines with very little effort. Open source. RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.
Event Store and RethinkDB belong to "Databases" category of the tech stack.
Some of the features offered by Event Store are:
- Functional Database
- Event-sourced applications
- Stores data
On the other hand, RethinkDB provides the following key features:
- JSON data model and immediate consistency.
- Distributed joins, subqueries, aggregation, atomic updates.
- Secondary, compound, and arbitrarily computed indexes.
RethinkDB is an open source tool with 22.5K GitHub stars and 1.75K GitHub forks. Here's a link to RethinkDB's open source repository on GitHub.
According to the StackShare community, RethinkDB has a broader approval, being mentioned in 53 company stacks & 166 developers stacks; compared to Event Store, which is listed in 9 company stacks and 11 developer stacks.
What is Event Store?
What is RethinkDB?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Event Store?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Event Store?
What are the cons of using RethinkDB?
Sign up to get full access to all the companiesMake informed product decisions
We initially chose RethinkDB because of the schema-less document store features, and better durability resilience/story than MongoDB In the end, it didn't work out quite as we expected: there's plenty of scalability issues, it's near impossible to run analytical workloads and small community makes working with Rethink a challenge. We're in process of migrating all our workloads to PostgreSQL and hopefully, we will be able to decommission our RethinkDB deployment soon.
High-speed update-aware storage used in our region server infrastructure; provides a good middle layer for storage of rapidly modified information.
Main database, using it in multiple datacenters in an active-active configuration.