Ross ROSS = Recommend OSS · open-source software intelligence for agents

RailsEventStore/rails_event_store

A Ruby implementation of an Event Store based on Active Record observed · 2026-08-28

github.com/RailsEventStore/rails_event_store · homepage · Ruby · MIT (permissive) observed · 2026-08-28

Health v2 · maintenance only

99/100

  • Activity 99
  • Release rhythm 99
  • 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: 23.5
  • age_days: 4173
  • days_rel: 7
  • days_push: 7
  • n_releases_24m: 11

Full methodology

Adoption not part of the score

1551 stars · 131 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

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

library · maturity stable

message-queue serialization logging middleware backend web-development developer-tools microservices ruby event-sourcing event-store cqrs domain-driven-design pubsub rails aggregate-root event-driven-architecture audit-log read-models web-server

6 sources

Member repositories

RepositoryRoleHealth v2
RailsEventStore/rails_event_storemain99

For agents

markdown · JSON · MCP: product_card(name="RailsEventStore/rails_event_store")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem