View a markdown version of this page

Overview: the systems, user journeys, and services hierarchy - AWS Resilience Hub

Overview: the systems, user journeys, and services hierarchy

The application modeling hierarchy in the next generation of Resilience Hub consists of three levels:

  • Systems – The top-level container representing a business application (for example, an e-commerce platform or a trading system).

  • User journeys – Critical business paths within a system (for example, "Path to purchase" or "Order fulfillment").

  • Services – The building blocks comprising AWS resources, code, and observability that support user journeys. A service belongs to exactly one system but can support multiple user journeys.

The following example shows a hierarchy for an e-commerce platform:


System (e.g., "E-commerce Platform")
├── User Journey: "Path to purchase"
│   ├── Service: "Auth Service"
│   ├── Service: "Checkout Service"
│   └── Service: "Payment Service"
├── User Journey: "Order fulfillment"
│   ├── Service: "Order Management Service"
│   └── Service: "Shipping Service"
└── Shared Service: "EKS Platform Service"
    (supports multiple user journeys)

You define where to find your AWS resources (AWS CloudFormation stacks, Terraform state files, resource tags, or Amazon EKS clusters), and the next generation of Resilience Hub automatically discovers and maps them into a topology showing how resources connect.