liveBook · Manning

Chapter 9: Architecture: The graph of programs and wires

What you will learn in chapter 9 of Crack Any Codebase with AI

This introduction defines multi-service architecture as a graph to reconstruct and previews a three-step AI process for mapping its components, stacks, and request wiring.

After this chapter you will be able to

What it builds on

Section by section

Introduction

This introduction defines multi-service architecture as a graph to reconstruct and previews a three-step AI process for mapping its components, stacks, and request wiring.

Key terms: single-process codebase, multi-service system, service graph, module-level architecture, docker-compose.yml, Procfile, Kubernetes manifests, environment variables, SDK client initializations, Terraform state

9.1 An architecture is a graph of programs and the wires between them

This section defines architecture as a service graph and shows how its nodes, connections, and shape reveal failure risks, trust boundaries, and build-versus-buy choices.

Key terms: architecture, graph, nodes, edges, service graph, synchronous, asynchronous, internal, public internet, internal asynchronous

9.2 Four sources hold the architecture

This section shows how to reconstruct an architecture by combining process declarations, environment configuration, application code, and Infrastructure-as-Code while treating configuration as evidence to verify.

Key terms: process declaration file, compose file, .env, application code, Infrastructure-as-Code, IaC, docker-compose.yml, Docker Compose, Procfile, Kubernetes manifests

9.3 Ask the agent to inventory every part from the config

This section shows how to use an AI agent to build a source-backed architectural inventory, classify each component by ownership, diagram its connections, and investigate the trade-offs revealed by the map.

Key terms: architectural inventory, runtime, source-backed, configuration files, environment variables, downstream nodes, CLIENT, RUN, RENT, CALL

9.4 Open each box to its real tech stack

This section shows how to turn abstract architecture-map nodes into actionable documentation of their real implementations, code locations, and operational trade-offs.

Key terms: Plain English, Under the Hood, Confirmation, node inventory, generic label, specific technology, protocol, file path, line number, tasker

9.5 Trace one request across the whole system

This section shows how to trace one core user request through a live architecture, distinguish synchronous from background work, compare runtime variants, and investigate risks a single trace hides.

Key terms: trace, core action, hop, node inventory, file:line, 200 OK, synchronous, asynchronous, user waits, queued for a worker

9.6 Summary

This summary gives a repeatable way to reconstruct a distributed system’s architecture by combining four evidence sources, inventorying components, investigating each one, and tracing a request end to end.

Concepts explained in this chapter

← Chapter 8: Interfaces: Where the product's verbs live

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.