eShop Reference Application
Explore the modeled order flow of dotnet/eShop through architecture maps, Event Storming boards and an order process diagram.
eShop Reference Application
What Was Modeled
Archally’s demonstration model describes the order flow of the .NET reference application dotnet/eShop. Its selected views show modeled service boundaries, commands, events, and the path from order placement through payment to shipping.
Explore the Model
Each artifact below presents a different question about the same model. These diagrams describe what the model states.
Demonstration model of the .NET reference application dotnet/eShop by Archally; not a product of its authors
Source: dotnet/eShop · MIT · (c) .NET Foundation and Contributors
-
Architecture map
How do the modeled eShop services connect?
-
Order in Software Design
Which commands and events carry an order?
-
Event Storming big picture
Which events describe the order journey?
-
Event Storming process
How do commands and events connect through the process?
-
System context
Who interacts with the eShop system?
-
Container architecture
Which containers collaborate inside eShop?
-
Domain boundaries
Which domains organize the eShop model?
-
Place, pay and ship
How does an order progress from placement to shipping?
Have a Similar Challenge?
If your team manages complex systems with scattered documentation, fragile integrations, or invisible change impact - let's talk about how a blueprint approach can help.
Discuss tool access and a bounded pilot