Incident VS eventstore

Compare Incident vs eventstore and see what are their differences.

Incident

Event Sourcing and CQRS library in Elixir (by pedroassumpcao)
Eventhandling event-sourcing Cqrs Elixir
Source Code
Docs
Suggest alternative
Edit details

eventstore

Event store using PostgreSQL for persistence (by commanded)
ORM and Datamapping Cqrs Eventstore Elixir event-sourcing Postgresql Database cqrs-es Commanded
Source Code
Suggest alternative
Edit details
InfluxDB
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors
Incident eventstore
- 2
154 1,009
- 1.3%
4.0 7.8
about 1 year ago about 1 month 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.

Incident

Posts with mentions or reviews of Incident. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning Incident 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
    7 projects | dev.to | 10 May 2022
    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
    6 projects | dev.to | 16 Jan 2022
    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 Incident and eventstore you can also consider the following projects:

event_bus - :surfer: Traceable, extendable and minimalist **event bus** implementation for Elixir with built-in **event store** and **event watcher** based on ETS.

rethinkdb - Rethinkdb client in pure elixir (JSON protocol)

wait_for_it - Elixir library for waiting for things to happen

ecto - A toolkit for data mapping and language integrated query.

goldrush - Small, Fast event processing and monitoring for Erlang/OTP applications.

amnesia - Mnesia wrapper for Elixir.

Seven Otters - The Seven Otters Library.

postgrex - PostgreSQL driver for Elixir

reaxive - Reactive Extensions for Elixir

extreme - Elixir Adapter for EventStore

mongo - MongoDB driver for Elixir

datomex - Elixir driver for the Datomic REST API

Incident vs event_bus eventstore vs rethinkdb Incident vs wait_for_it eventstore vs ecto Incident vs goldrush eventstore vs amnesia Incident vs Seven Otters eventstore vs postgrex Incident vs reaxive eventstore vs extreme eventstore vs mongo eventstore vs datomex