Skip to content

C4 and ArchiMate — Reading Guide

What C4 and ArchiMate Actually Are

The first thing to know is that C4 and ArchiMate aren't really the same kind of thing.

C4 isn't a modeling language in any technical sense. It has no metamodel of the kind ArchiMate has, no formal relationship semantics, no derivation rules. Simon Brown himself describes C4 as "an abstraction-first approach to diagramming software architecture" — abstractions and diagrams, not a language. Comparing it to ArchiMate is roughly like comparing a sketching convention to a formal grammar. They aren't peers in any technical sense.

ArchiMate, by contrast, is a full enterprise architecture modeling language. It has a formal metamodel with typed elements, typed relationships, derivation rules, and a viewpoint mechanism. Its concepts span strategy, motivation, business, application, technology, and implementation & migration — six layers covering the full range of stakeholders an EA practice engages, from board-level strategy through business process owners to infrastructure teams. Its scope is the entire enterprise; C4's scope is one or a small number of software systems.

Teams compare them anyway, because they face a real choice — where to put their architecture-documentation effort, and what notation to use. That choice is legitimate. But the comparison only makes sense once you understand what each one is, and the three articles below work through that, from the underlying tension to the practical consequences.

These three articles form a trilogy. Each tackles the C4-vs-ArchiMate question from a different angle, and each presupposes you've accepted the previous one's conclusion.

The Three Articles - Suggested Reading Order

# Article Question it answers Angle
1 Diagramming Approach Meets Modeling Language Why is this debate so heated? Surfaces the underlying tension by arguing both extremes — "ArchiMate makes C4 unnecessary" vs "C4 is essential." - Philosophical.
2 A Practitioner's Guide How do we organize a practice that uses both? Decision framework, ownership model, integration strategies, and team scenarios. - Strategic.
3 ArchiMate Application Layer vs C4 Containers What goes in ArchiMate vs C4 when I'm modeling? Patterns, anti-patterns, decision matrix - Tactical.

How They Fit Together

flowchart TD
    A["1. Diagramming Approach Meets Modeling Language. Should we even use both?"]
    B["2. Practitioner's Guide. How do we organize the practice?"]
    C["3. Application Layer vs Containers. What goes where when I model?"]
    A -->|builds toward| B
    B -->|builds toward| C

Pick Your Entry Point

You Probably Don't Need This Trilogy If...

You're using only one of the two notations and have no plans to introduce the other. The trilogy is for organizations weighing both, using both, or transitioning between them.