Popularity

6.2

Growing

Activity

9.5

Declining

Stars 1,109

Watchers 33

Forks 103

Last Commit 2 days ago

Description

An implementation of an Event Store for Ruby and Rails. Comes with Active Record adapter.

This single repository hosts several gems.

Monthly Downloads: 184,769

Programming language: Ruby

License: MIT License

Tags: Abstraction Architecture Event-Driven CQRS Event Sourcing

Latest version: v1.2.2

Rails Event Store alternatives and similar gems

Based on the "Abstraction" category.
Alternatively, view Rails Event Store alternatives based on common mentions on social networks and blogs.

Trailblazer

8.4 3.6 L5 Rails Event Store VS Trailblazer

The advanced business logic framework for Ruby.
Cells

8.4 3.2 L5 Rails Event Store VS Cells

View components for Ruby and Rails.

Deliver Cleaner and Safer Code - Right in Your IDE of Choice!

SonarLint is a free and open source IDE extension that identifies and catches bugs and vulnerabilities as you code, directly in the IDE. Install from your favorite IDE marketplace today.

Promo www.sonarlint.org

Interactor

8.3 3.6 L5 Rails Event Store VS Interactor

Interactor provides a common interface for performing complex user interactions.
wisper

8.2 0.0 Rails Event Store VS wisper

A micro library providing Ruby objects with Publish-Subscribe capabilities
Responders

7.5 6.5 L2 Rails Event Store VS Responders

A set of Rails responders to dry up your application
Decent Exposure

7.2 0.0 L5 Rails Event Store VS Decent Exposure

A helper for creating declarative interfaces in controllers
ActiveInteraction

7.1 5.7 L5 Rails Event Store VS ActiveInteraction

:briefcase: Manage application specific business logic.
Mutations

6.5 1.7 L5 Rails Event Store VS Mutations

Compose your business logic into commands that sanitize and validate input.
dry-types

5.7 7.8 L5 Rails Event Store VS dry-types

Flexible type system for Ruby with coercions and constraints
Amoeba

5.1 3.7 Rails Event Store VS Amoeba

A ruby gem to allow the copying of ActiveRecord objects and their associated children, configurable with a DSL on the model
Apotomo

5.1 0.0 L5 Rails Event Store VS Apotomo

MVC Components for Rails.
Light Service

5.1 5.6 L5 Rails Event Store VS Light Service

Series of Actions with an emphasis on simplicity.
SimpleCommand

4.8 5.8 Rails Event Store VS SimpleCommand

A simple, standardized way to build and use Service Objects (aka Commands) in Ruby
Rectify

4.7 0.0 L5 Rails Event Store VS Rectify

Build maintainable Rails apps
Waterfall

4.6 0.0 L5 Rails Event Store VS Waterfall

A slice of functional programming to chain ruby services and blocks, thus providing a new approach to flow control. Make them flow!
Sequent

4.4 8.6 Rails Event Store VS Sequent

CQRS & event sourcing framework for Ruby
dry-transaction

4.2 7.6 Rails Event Store VS dry-transaction

Business transaction DSL
u-service

4.0 3.9 Rails Event Store VS u-service

Represent use cases in a simple and powerful way while writing modular, expressive and sequentially logical code.
Clowne

3.2 5.1 Rails Event Store VS Clowne

A flexible gem for cloning models
PageletRails

2.8 0.0 L5 Rails Event Store VS PageletRails

Improve perceived performance of your rails application with minimum effort
Surrounded

2.6 0.0 L5 Rails Event Store VS Surrounded

Create encapsulated systems of objects and focus on their interactions
Setsy

2.3 0.0 Rails Event Store VS Setsy

Settings for classes backed by a database with defaults.
Smart Init - Simple service objects in Ruby

2.3 0.6 Rails Event Store VS Smart Init - Simple service objects in Ruby

A simple gem for eliminating Ruby initializers boilerplate code, and providing unified service objects API
Rocketman

2.1 0.0 Rails Event Store VS Rocketman

🚀 Rocketman help build event-based/pub-sub code in Ruby
SuperModule

2.1 0.0 Rails Event Store VS SuperModule

SuperModule allows defining class methods and method invocations the same way a super class does without using def included(base). This also succeeds ActiveSupport::Concern by offering lighter syntax
skinny_controllers

1.9 0.0 L5 Rails Event Store VS skinny_controllers

A pattern for allowing for easier testing of large projects' business logic
Pathway

1.6 0.0 Rails Event Store VS Pathway

Define your business logic in simple steps
Strategic

1.2 3.2 Rails Event Store VS Strategic

Strategic - Painless Strategy Pattern in Ruby and Rails
Invokable

1.2 0.0 Rails Event Store VS Invokable

Objects are functions! Treat any Object or Class as a Proc (like Enumerable but for Procs).
Lionshare

0.7 0.0 Rails Event Store VS Lionshare

A Ruby interface to the Lionshare API (cryptocurrency prices)
EasilyTypable

0.6 0.0 Rails Event Store VS EasilyTypable

Ruby module that facilitates English-like type checking in an inheritance hierarchy via "type_name?" methods
grpc_serializer

0.2 2.1 Rails Event Store VS grpc_serializer

A simple library to encode nested hash to grpc object and vice versa
simple_active_link_to

0.1 7.2 Rails Event Store VS simple_active_link_to

Simple rails view helper to manage "active" state of a link
SolidService

- 10.0 Rails Event Store VS SolidService

A servcie pattern with a simple API
dry-rb

- Rails Event Store VS dry-rb

dry-rb is a collection of next-generation Ruby libraries, each intended to encapsulate a common task.

* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.

Do you think we are missing an alternative of Rails Event Store or a related project?

Add another 'Abstraction' Gem

Popular Comparisons

README

Rails Event Store

Rails Event Store (RES) is a library for publishing, consuming, storing and retrieving events. It's your best companion for going with an event-driven architecture for your Rails application.

You can use it:

as your Publish-Subscribe bus to decouple core business logic from external concerns in Hexagonal style architectures as an alternative to ActiveRecord callbacks and Observers as a communication layer between loosely coupled components to react to published events synchronously or asynchronously to extract side-effects (notifications, metrics etc) from your controllers and services into event handlers to build an audit-log to create read-models to implement event-sourcing