System Design documentation

Learn to map integrations, data, events, delivery pipelines, security, observability, and infrastructure.

AAL System Design 0.2 · Dictionary 0.2.0

Start here

System Design helps you explain how the parts of a system work together. You can map a customer calling a service, data moving between applications, or software running on infrastructure.

Start with two boxes and a connection: Customer → Orders API. Each box is a element; the connection describes their interaction. You can build this visually or write AAL in the source editor. Both edit the same model.

What can you describe?

  • Application integrations and request flows.
  • Data pipelines, events, and delivery pipelines.
  • Security, observability, and cloud or on-premises infrastructure.

Choose your learning path

New to System Design? Follow Getting started, then the Workspace tour. Build a small connection before adding containment or reusable software.

Learn by building

  1. Create and connect two elements in Getting started.
  2. Use the Workspace tour to rename the API and inspect the connection.
  3. Read Elements and nesting to learn children and collapse/expand before optional catalog detail.
  4. Use Relationships and styling to refine communication and readability.
  5. Save, export, and present your work.

Choose another entry point

  • Prefer source? Read the language reference and copy a complete example into a new project. Check diagnostics and compare the canvas.
  • Looking for a specific product? Search the element dictionary by name, role, provider, or type ID.
  • Need a larger design? Explore the purpose-based, provider-specific, and hybrid examples.