Software Architecture Patterns - Understanding Common Architecture Patterns and When to Use Them

Sep 22, 2026

Upload by Ophelia

Software architecture patterns explain how to define an application’s core characteristics and behavior when formal architecture is missing. It addresses common failure modes such as tightly coupled, brittle systems that are hard to scale, change, deploy, or reason about. The book guides architects and developers to justify architectural decisions by comparing strengths and weaknesses across patterns, then applying them to specific business needs and goals.

LanguageEnglish

CategoryTechnology

FormatPDF

Pages54

Reading Time2 h 16 min

AccessFree to download

Introduction

Layered Architecture

Pattern Description

Event-Driven Architecture

Mediator Topology

Broker Topology

Microkernel Architecture

Pattern Description

Pattern Examples

Microservices Architecture Pattern

Pattern Description

Pattern Topologies

Avoid Dependencies and Orchestration

Space-Based Architecture

Pattern Description

Pattern Dynamics

Pattern Analysis Summary

Software Architecture Patterns Understanding Common Architecture Patterns and When to Use Them Mark Richards Software Architecture Patterns by Mark Richards Copyright © 2015 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles ([http://oreilly.com/safari](http://oreilly.com/safari)). For more information, contact our corporate/institutional sales department: 800-998-9938 or [corporate@oreilly.com](corporate@oreilly.com). Editor: Heather Scherer Production Editor: Colleen Lobner Copyeditor: Amanda Kersey Interior Designer: David Futato Cover Designer: Ellie Volckhausen Illustrator: Rebecca Demarest February 2015: First Edition Revision History for the First Edition 2015-02-24: First Release 2015-03-30: Second Release 2017-06-22: Third Release The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. Software Architec‐ ture Patterns, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. While the publisher and the author have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the author disclaim all responsibility for errors or omissions, including without limi‐ tation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsi‐ bility to ensure that your use thereof complies with such licenses and/or rights. 978-1-491-92424-2 [LSI] Table of Contents Introduction................................................... v 1. Layered Architecture......................................... 1 Pattern Description 1 Key Concepts 3 Pattern Example 5 Considerations 7 Pattern Analysis 8 2. Event-Driven Architecture................................... 11 Mediator Topology 11 Broker Topology 14 Considerations 17 Pattern Analysis 18 3. Microkernel Architecture.................................... 21 Pattern Description 21 Pattern Examples 23 Considerations 24 Pattern Analysis 25 4. Microservices Architecture Pattern............................ 27 Pattern Description 27 Pattern Topologies 29 Avoid Dependencies and Orchestration 32 Considerations 33 Pattern Analysis 34 5. Space-Based Architecture.................................... 37 Pattern Description 38 Pattern Dynamics 39 Considerations 42 Pattern Analysis 43 A. Pattern Analysis Summary................................... 45 Introduction It’s all too common for developers to start coding an application without a formal architecture in place. Without a clear and welldefined architecture, most developers and architects will resort to the de facto standard traditional layered architecture pattern (also called the n-tier architecture), creating implicit layers by separating source-code modules into packages. Unfortunately, what often results from this practice is a collection of unorganized source-code modules that lack clear roles, responsibilities, and relationships to one another. This is commonly referred to as the big ball of mud architecture anti-pattern. Applications lacking a formal architecture are generally tightly cou‐ pled, brittle, difficult to change, and without a clear vision or direc‐ tion. As a result, it is very difficult to determine the architectural characteristics of the application without fully understanding the inner-workings of every component and module in the system. Basic questions about deployment and maintenance are hard to answe

FAQs

Why do software teams need architecture patterns instead of starting with code directly?

Developers often begin without a formal architecture, which can lead to unorganized modules with unclear roles and relationships. Architecture patterns help define consistent behavior and characteristics, making systems easier to understand and evolve.

What key questions does the book highlight when evaluating an application’s architecture?

It emphasizes questions about scalability, performance characteristics, responsiveness to change, deployment characteristics, and how responsive the architecture is overall.

How does the book approach choosing an architecture pattern for specific business needs?

It explains that each architecture pattern has strengths and weaknesses and that architects must justify their decisions. The goal is to provide enough information to make and support that choice.

Sep 22, 2026

Upload by Ophelia