THE DIAGRAM LIBRARY / 10 WORKED EXAMPLES
Ten worked examples, each with its own layout grammar. Inspect a real SVG, try the three audience densities and choose a neighboring diagram when your question changes.
Topology, change, protocols, decision logic and data models. Choose the representation that matches the level you are reviewing.
Make a microservice system readable without losing its topology. Start with a ten-node commerce example, then inspect request routing, dedicated storage and asynchronous analytics across a quiet, tiered layout.
Open designerExplain a system change using synchronized Before, Changes and After panels. The ten-node example replaces a direct dispatcher with a durable queue while retaining storefront, worker and storage identities.
Open designerMake a checkout trace legible with ordered messages, dashed lifelines and correctly encoded returns. Eight participants are split into authorization and fulfillment traces, with an explicit handoff between them.
Open designerSeparate action steps from decisions in an eight-node checkout flow. Follow the valid-cart path, inspect the named Yes/No exits and trace the repair loop without letting it cut across the main process.
Open designerExplain the commerce domain using eight conceptual entities and explicit relationship cardinalities. Keep Customer, Order, Line item and Product meanings separate from implementation-level SQL constraints.
Open designerReview eight illustrative commerce tables in two four-table subsystems. Read physical table names, SQL types and key constraints, then trace foreign keys from the source column row to the referenced primary-key row.
Open designerStrategy, ownership and dates. Separate where a capability sits from who acts and when the work happens.
Map an eight-component value chain against Genesis, Custom-built, Product and Commodity. Explore an illustrative search capability moving toward product maturity while keeping commodity infrastructure in the background.
Open designerMake ownership visible across Customer, Support, Warehouse and Finance. The eight-step return example distinguishes team activities from the handoffs that move the item toward inspection, refund and notification.
Open designerRead a ten-day example launch schedule with eight tasks across Discovery, Build and Release. A shared date axis makes overlap visible while one launch bar provides focus without adding a tangle of dependency arrows.
Open designerQuantities that split and merge. Keep scale and conservation visible rather than reducing a measured flow to arrows.
Worked examples use illustrative data. Edited sources require an AI provider; cached previews are ready immediately.
EditorialDiagram