So you are a fan of Domain Driven Design
and you know what Event Sourcing is.
You are about to start new exciting green field project
or you still working on legacy but profitable one.
You need some allies
Business will be happy to be understood by developers
...and finally to understand developers
Build the right features...
Easier to maintain & change...
Focus on the most important ones.
Just start publishing domain events
... but remember to store them.
Implement small feature without asking for approval.
There are areas where business already do ES forced by law.
Correlation & Causations ids to know all paths.
You all need to understand the solution.
CRUDy mindset won't fit.
It's not one way.
All works fine in on my machine.
But might fail under heavy load.
... that commands are shipped to them by sea freight
... they prevent my mac’s lid from closing
... that every operation raises concerns under EU antitrust regulations
... it takes two camels to carry them
... they have timezones
... that every business rule has its own legal department
That's just Business As Usual
Talk to you domain experts
by Greg Young
Google search results
Your DropBox files
Even Your bank account
at least for business apps
Similar solutions available
Beware of frameworks
Build your adapters (anti-corruption layer)
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.