# RailsEventStore/rails_event_store

A Ruby implementation of an Event Store based on Active Record

Repository: https://github.com/RailsEventStore/rails_event_store
Canonical: https://ross.abutalabs.com/products/rails_event_store
Homepage: http://railseventstore.org
Language: Ruby
License: MIT
License Family: permissive
Topics: ruby, event-sourcing, rails, ddd, aggregate-root, event-driven, domain-driven-design, event-driven-architecture, cqrs-es, cqrs
Last push: 2026-08-26T18:06:09+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 99, longevity 100
- inputs: {"age_days": 4173, "days_push": 7, "days_rel": 7, "gap_med": 23.5, "n_releases_24m": 11}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1551, forks 131 (observed 2026-08-28T04:05:02.179473+00:00)

## What it is
Rails Event Store (RES) is a Ruby library for publishing, consuming, storing, and retrieving domain events, built on Active Record. It serves as a publish-subscribe bus and event store for implementing event-driven architectures, event sourcing, CQRS, and audit logs in Rails applications.

## Use cases
- implement event sourcing in a Rails application
- replace ActiveRecord callbacks and observers with domain events
- decouple core business logic from external concerns in hexagonal architecture
- build an audit log of domain events
- create read models with CQRS
- publish and subscribe to events synchronously or asynchronously
- extract side-effects like notifications and metrics into event handlers
- communicate between loosely coupled components

## When to choose
- you are building a Rails application and want event-driven architecture
- you need event sourcing or CQRS with Active Record as the persistence layer
- you want to decouple domain logic from framework concerns like callbacks and observers
- you need a pub-sub event bus with sync/async handlers inside a monolith

## When to avoid
- you need a standalone distributed event broker across services (consider Kafka or a dedicated event store)
- your project is not Ruby/Rails based
- you only need simple background job processing without event semantics
- you require non-ActiveRecord databases without an adapter

## Facets
- artifact type: library
- maturity: stable
- function: message-queue, serialization, logging, middleware
- domain: backend, web-development, developer-tools, microservices
- platform: ruby
- tags: event-sourcing, event-store, cqrs, domain-driven-design, pubsub, rails, aggregate-root, event-driven-architecture, audit-log, read-models, web-server

## Member repositories
- RailsEventStore/rails_event_store (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:02.179473+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:30:15.103019+00:00, confidence not recorded.
  - readme: https://github.com/RailsEventStore/rails_event_store (fetched 2026-08-28T04:05:02.179473+00:00, sha 9a0396cf2361)
  - homepage: http://railseventstore.org (fetched 2026-08-29T11:30:48.215976+00:00, sha c330657f00ae)
  - site_page: https://railseventstore.org/docs/getting-started/introduction (fetched 2026-08-29T11:30:48.225271+00:00, sha 9d5e13357831)
  - site_page: https://railseventstore.org/docs/master/getting-started/introduction (fetched 2026-08-29T11:30:48.227319+00:00, sha 4921704a1e2e)
  - site_page: https://railseventstore.org/docs/2.19.3/getting-started/introduction (fetched 2026-08-29T11:30:48.229496+00:00, sha 1b593531e020)
  - site_page: https://railseventstore.org/docs/1.3.1/getting-started/start (fetched 2026-08-29T11:30:48.231320+00:00, sha a2ba924263d4)
- Data as of 2026-08-30T08:39:29.467469+00:00.