Software architecture for developers who just became architects

12 steps · about 4 h 35 min · Intermediate

  1. Who Needs an Architect? (article, Martin Fowler, IEEE Software, 10 min)

    It starts with the question the role raises: what architecture is, and who decides what counts as important.

  2. Software Architecture Guide (guide, Martin Fowler, 30 min)

    It gives you the shared vocabulary of the field and a map of the topics you'll be expected to know.

  3. Software Architecture for Developers (free online sample: chapters 4 and 5) (guide, Simon Brown, Leanpub, 40 min)

    These chapters cover the architecture role. They stress that it is a role, not a rank, which is a useful frame if you were handed it without warning.

  4. Conway's Law (article, Martin Fowler, 10 min)

    It shows that part of the job is shaping teams and communication, because system design follows how people are organized.

  5. The C4 Model for Software Architecture (article, Simon Brown, InfoQ, 20 min)

    It teaches you to draw clear context, container, component and code diagrams, which is how you communicate a design to others.

  6. Monolith First (article, Martin Fowler, 10 min)

    It is a short, concrete example of an architect's judgment call, and a good protection against fashionable over-engineering.

  7. Microservice Trade-Offs (article, Martin Fowler, 25 min)

    It trains you to weigh costs against benefits instead of copying trends, which is the core skill of architecture.

  8. Maintain an architecture decision record (ADR) (doc, Microsoft Learn, 15 min)

    It turns judgment into a habit: write down each significant decision, the alternatives you ruled out, and the trade-offs.

  9. Architecture decision record (ADR) examples (repo, GitHub, architecture-decision-record, 25 min)

    It provides ready-made templates and examples, so you can write your first ADR in your own repository.

  10. arc42 Template Overview (reference, arc42, 20 min)

    It gives you a free, 12-section structure for documenting a whole system, with ADRs as one section.

  11. Practical tips and examples for the arc42 template (reference, arc42 docs, 30 min)

    It has tips for each section, so you can fill in a real architecture document for your own system.

  12. The Modern Architect - The Architect Elevator (blog, Gregor Hohpe, 40 min)

    It finishes with the soft side of the job: connecting engineering detail to business strategy and communicating up and down the organization.