commanded/eventstore
Event store using PostgreSQL for persistence observed · 2026-08-28
Health v2 · maintenance only
66/100
- Activity 80
- Release rhythm 28
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 55
- age_days: 3845
- days_rel: 545
- days_push: 121
- n_releases_24m: 4
Adoption not part of the score
1162 stars · 155 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
An event store library for Elixir that uses PostgreSQL as its underlying persistence engine. It supports appending and reading event streams, subscriptions, and running on a cluster of nodes.
Use cases
- implement event sourcing in an Elixir application
- store append-only event streams in PostgreSQL
- build a CQRS system with Elixir
- subscribe to events from an event stream
- run an event store across a cluster of nodes
When to choose
- you're building an Elixir app with event sourcing or CQRS
- you want to use PostgreSQL as your event store instead of a dedicated event store database
- you need persistent or transient subscriptions to event streams
When to avoid
- you're not using Elixir or the BEAM ecosystem
- you need a standalone event store server like EventStoreDB or Kafka
- your persistence model doesn't fit append-only event streams
Facets
library · maturity active
database serialization message-queue databases backend developer-tools elixir windows event-sourcing cqrs eventstore postgresql elixir event-streaming subscriptions linux macos
1 source
- readme: https://github.com/commanded/eventstore · fetched 2026-08-28 · 63c2cb40168d
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| commanded/eventstore | main | 66 |
For agents
markdown · JSON · MCP: product_card(name="commanded/eventstore")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem