When building a serverless application or migrating one, understanding where the boundaries between systems are can be very difficult. If wrong, fall into the trap of distributed monolith. Ending in a place where you cannot deploy independently and teams block each other.

EventBridge Storming is a workshop that helps teams to design loosely coupled Serverless Event-Driven architectures on AWS. As an extension to EventStorming, a Domain-Driven Design technique, EventBridge Storming takes things further - leaving teams with the blueprint for their Serverless architecture. Aleios use this technique with companies of all sizes, from startups building greenfield through to global enterprises migration all the way from on-prem (as part of our "Minimum Viable Migration" framework). ‍ EventBridge storming was released in 2020 by Ben Ellerby, Founder and CTO of aleios, and has been used with our clients and the wider Serverless community.

An 8 Step Process:

1. Event discovery - Discover the set of real world business events.
2. Temporal Sequencing - Put the events in time order
3. Trigger Detection - Find the commands and actors
4. Categorise Aggregates - Find the entities
5. Categorise Bounded Context - Group the events, avoiding dependencies
6. Name Microservices - Avoiding 1-1 bounded contexts
7. Create Event Bus - Create a single event bus
8. Create shared Schema - Share a structure of events between services