What do you think?
Rate this book
The C4 model for visualising software architecture
The book The C4 model for visualising software architecture goes over how we should divide the language we use based on the level of granularity we are trying to explain and that we should never mix those levels in a conversation. By using a common vocabulary we can leave better documentation behind us and improve onboarding. It proposes a starting point of 4 levels: Context, Container, Component and Code but since projects can defer in scope it also provides alternatives.
ebook
Published February 24, 2023
6 people are currently reading
44 people want to read
About the author
Simon Brown
8 books63 followersSimon is an independent software development consultant specializing in software architecture - specifically technical leadership, communication, and lightweight, pragmatic approaches to software architecture. Simon is the author of "Software Architecture for Developers", a developer-friendly guide to software architecture, technical leadership, the balance with agility and communicating software architecture with sketches, diagrams, and models. He is also the creator of the C4 software architecture model and the founder of Structurizr, a SaaS product to create web-based software architecture diagrams using code.
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 3 of 3 reviews
February 11, 2024
Brief and to the point.
A nicely laid out and explained methodology for using the author's C4 model for creating software and infrastructure diagrams.
A nicely laid out and explained methodology for using the author's C4 model for creating software and infrastructure diagrams.
December 6, 2025
This is a very easy to read and simple architecture book. For that alone it deserves a good rating.
My only gripe with the book, and something you should include in the coming O'Reilly edition if its not to late to edit it.
No where in the entire book do you have a visual representation of a Key/Legend. Every second page says "Add it to the Key/Legend so your reader doesn't get confused!".
I finished the book and was confused about what the 'best' way was to actually write and display a legend. A quick inclusion of a few examples would do wonders there.
My only gripe with the book, and something you should include in the coming O'Reilly edition if its not to late to edit it.
No where in the entire book do you have a visual representation of a Key/Legend. Every second page says "Add it to the Key/Legend so your reader doesn't get confused!".
I finished the book and was confused about what the 'best' way was to actually write and display a legend. A quick inclusion of a few examples would do wonders there.
August 4, 2025
A refreshing new perspective on software development and how to model.
Displaying 1 - 3 of 3 reviews