redo
pipelined erlang redis client (by heroku)
eventstore
Event store using PostgreSQL for persistence (by commanded)
redo | eventstore | |
---|---|---|
- | 2 | |
19 | 1,010 | |
- | 0.8% | |
0.0 | 7.5 | |
over 5 years ago | 5 days ago | |
Erlang | Elixir | |
MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
redo
Posts with mentions or reviews of redo.
We have used some of these posts to build our list of alternatives
and similar projects.
We haven't tracked posts mentioning redo yet.
Tracking mentions began in Dec 2020.
eventstore
Posts with mentions or reviews of eventstore.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-10.
-
Using CQRS in a simple Phoenix API with Commanded
Since I already had a Postgres database running, I decided to use EventStore rather than installing and babysitting EventStoreDB. To initialize the database and tables, I ran mix event_store.init and mix event_store.create.
-
Phoenix LiveView, but event-sourced
My goal is to use LiveView to update a price chart as trades are executed by the system. A LiveView process is a lot like a GenServer, with a bespoke process for each client, executing handle_* functions as the client does things. The first step to real-time chart updates is to trigger one of these handler functions in my LiveView controller when a trade is executed. I'm using Commanded's own EventStore library to dispatch and store my events, so their documentation is the place to start.
What are some alternatives?
When comparing redo and eventstore you can also consider the following projects:
triton - a Cassandra ORM for Elixir
rethinkdb - Rethinkdb client in pure elixir (JSON protocol)
eredis - Erlang Redis client
ecto - A toolkit for data mapping and language integrated query.
boltun - Transforms notifications from the Postgres LISTEN/NOTIFY mechanism into callback execution
amnesia - Mnesia wrapper for Elixir.
redix - Fast, pipelined, resilient Redis driver for Elixir. 🛍
postgrex - PostgreSQL driver for Elixir
mongodb - MongoDB driver for Elixir
extreme - Elixir Adapter for EventStore
diver - A HBase driver for Erlang/Elixir using Jinterface and the Asynchbase Java client to query the database.
mongo - MongoDB driver for Elixir