liveBook · Manning

Scenario

As explained in Microservices Patterns, Second Edition

A scenario is a description of an application's dynamic behavior across elements represented in its architectural views.

An architectural scenario describes dynamic behavior by showing how elements in architectural views interact. It connects static structure to system behavior and requirements. section 3.2 section 3.2.5

Scenarios serve different purposes across architectural views:

  • For domain, component, and deployment views, trace the sequence of interactions that implements a system operation or user story. section 3.2.5
  • For the build view, describe how changes flow from a developer’s laptop to production. section 3.2.5
  • Identify architecturally significant scenarios when they capture an application’s essence or impose technical requirements that shape its architecture. section 3.2.5

Food to Go

Ordering, preparation, and delivery scenarios are architecturally significant because they capture the essence of the application. section 3.2.5

Figure 3.12 A sequence diagram for the createOrder() operation that shows how the API Gateway, Order Service, Consumer Service, and Kitchen Service collaborate to implement the operation
self contained order taking

A sequence diagram traces how the API Gateway, Order Service, Consumer Service, and Kitchen Service collaborate to create an order. section 3.2.5

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines scenarios as interaction sequences and distinguishes operational flows from build-to-production change flows.
Examples
Uses Food to Go ordering, preparation, and delivery, plus a create-order service interaction sequence.
What it assumes
Assumes architectural elements and static views, while defining how scenarios animate those structures.
What you can do after
Understand how architectural elements collaborate to implement system behavior and requirements.
How it connects
Links architectural scenarios to static views, system operations, user stories, and deployment pipelines.

Also explained in

Compare how 7 books explain scenario →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.