eventstore
Event store using PostgreSQL for persistence (by commanded)
conduit
RealWorld example backend implementing the CQRS/ES pattern in Elixir and Phoenix (by slashdotdash)
eventstore | conduit | |
---|---|---|
2 | 1 | |
1,010 | 337 | |
0.9% | - | |
7.5 | 10.0 | |
7 days ago | about 3 years ago | |
Elixir | 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.
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.
conduit
Posts with mentions or reviews of conduit.
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
There's an example application called Conduit, which is the source code for an eBook's project, but its guidance is not up to date and the book itself starts with account / user management (a pretty advanced domain). The other resource outside of the package documentation is a 20 minute conference talk from 2018.
What are some alternatives?
When comparing eventstore and conduit you can also consider the following projects:
rethinkdb - Rethinkdb client in pure elixir (JSON protocol)
commanded - Use Commanded to build Elixir CQRS/ES applications
ecto - A toolkit for data mapping and language integrated query.
amnesia - Mnesia wrapper for Elixir.
postgrex - PostgreSQL driver for Elixir
extreme - Elixir Adapter for EventStore
mongo - MongoDB driver for Elixir
datomex - Elixir driver for the Datomic REST API
riak - A Riak client written in Elixir.
arc_ecto - An integration with Arc and Ecto.
shards - Partitioned ETS tables for Erlang and Elixir
esqlite - Erlang NIF for sqlite