Martin Fowler's Website

What the architecture guide contains

Martin Fowler is chief scientist at Thoughtworks and one of the people who shaped the modern vocabulary of software design. The page linked here is his architecture guide, which gathers his and his colleagues' writing in two groups:

• Application architecture: the microservices guide, micro frontends, GUI architectures, serverless architectures, presentation domain data layering, feature toggles, patterns of legacy displacement and modularising React applications.
• Enterprise architecture: enterprise architects joining teams, integrated business and technology strategy, products over projects, the architect elevator and enterprise integration using REST.

It also links to the Catalog of Patterns of Distributed Systems, which describes recurring solutions such as write ahead logs, leader and followers, and quorums in a consistent, readable format.

Fowler's own definition sets the tone: architecture is "about the important stuff. Whatever that is", and it is the shared understanding that expert developers have of a system's design.

Why go to the source

Terms like microservice, strangler fig, event sourcing and continuous delivery are used loosely in blog posts and job ads. The original articles are almost always more precise and more cautious. Reading them often reveals that the authors explicitly warned against the thing you have seen the idea used for. For example, the microservices material comes with prerequisites and a "monolith first" argument that many teams skip.

What to read first

1. The microservices guide, including the original microservices article and the piece on microservice prerequisites.
2. Monolith first, a short argument for starting with a well structured monolith.
3. Patterns of legacy displacement, if you work on an older system that needs replacing gradually.
4. Feature toggles, one of the clearest long form pieces on the topic.
5. One or two entries from patterns of distributed systems, such as write ahead log or leader and followers.

That selection takes a few evenings and gives you a solid, well sourced grounding.

Is it worth it compared with courses?

It is free, carefully written and has no sales agenda. What it lacks is structure: there is no course order, no exercises and no single narrative. Use it as a set of primary sources alongside a book or course rather than instead of one. It is also not interview preparation; it gives you the reasoning, not a script.

Weak spots

• Some articles are old. The ideas usually hold, but tool examples can be dated. Check the publication date at the top of each piece.
• Many articles are written by guest authors from Thoughtworks, so quality and depth vary slightly.
• The site is broad. Without a reading plan it is easy to wander.

Pair it with

• Fowler's books, such as Refactoring and Patterns of Enterprise Application Architecture, for depth.
• Fundamentals of Software Architecture for a structured view of styles and trade offs.

Best for: engineers who want the original arguments rather than summaries, and anyone forming an opinion on service architecture or legacy migration.