Tracking Issue for 1.0

[ryan-mars]

Overview

The following issues track discussion and implementation of key features of Stochastic for Event Storm -> Code.

• Event Event #4

• Policy Policy #10

• Command & Handler Command & Handler #8

• Aggregate Store (Aggregate) #11

• Bounded Context Bounded Context #7

• Read Model & Projection Read Model & Projection #6

• Query a Read Model Query #5

• External Service External Service #2

• AWS Serverless & CDK Infrastructure AWS: Serverless runtime & CDK infrastructure #12

• Event replay Event replay #9

• Event storm visualization Event Storm Visualization #3

• Pan Am Airline example app Pan Am Airline example app #13

• event storm is decoupled from runtime architecture and infrastructure provider

• fluent interface matching event storming output

Event Storming

Illustration ©️ Avanscoperta

Sample use case

The utility of stochastic would be best demonstrated through a useful example app. We'll resurrect Pan-Am airlines for this.

The story goes roughly like this:

• Scheduler adds flights to schedule
• I book a ticket
• I select dates, origin, destination
• I select my seat (contention around resources)
• I pay
• I cancel my ticket
• Seat is released
• Cancellation policy does different stuff depending on your status level
• Refund
• Credit
• I check in (traveler)
• I board (gate agent)
• Dispatcher does out, up, on, in
• Loyalty policy awards points
• Dispatcher cancels flight
• Deplane
• Manifest is cleared
• Rebooking policy rebooks according to status

Big Picture

Process Model

Software model

[sam-goodwin]

What features are we missing from the current state of the code to support this tracer bullet? A model/pattern for external systems? A consistency model for an aggregate, i.e. Seating?

[ryan-mars]

Updated the Even Storm to add Software model

[ryan-mars]

@sam-goodwin I'm going to start implementing the demo and find out. Off the top of my head...

• Bounded Context types/infra/runtime
• Partition event storm into multiple Cfn stacks
• Event subscription across bounded contexts infra/runtime
• Aggregate types/infra/runtime
• Event replay types/infra/runtime
• Command infra/runtime
• Read model infra/runtime
• Query infra/runtime

[sam-goodwin]

Partition event storm into multiple Cfn stacks

A single event storm in multiple stacks? Or should a single event storm be tied to a stack? Is this modeled on the declarations of commands/events/policies/etc. or is it where the infrastructure interpreter is configured? Let's create an issue to track each of these items so we can have a detailed discussion and record our decisions.

[ryan-mars]

A single event storm in multiple stacks?

Moving discussion to Bounded Context #7