Image for post
Image for post

In most of my projects, I’m using or I’m trying to introduce patterns from Domain-Driven Design, Event Sourcing, and CQRS. Most of those patterns are somehow related to the publish-subscribe pattern and it’s not possible to efficiently use them without it. I’m working with Ruby on Rails and my choice is RailsEventStore. Of course, it’s possible to implement a very basic mechanism by ourselves, but if we can use a well-tested solution then why not use it. The general idea behind this article should be applicable for every tool but in the examples, RES will be used.

Let’s start from the beginning. We start a new project or maybe we want to extract our first bounded context from existing legacy code. We need to add event store configuration to the project. …


Mariusz Kapcia

I’m a Ruby on Rails developer :)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store