Software Architecture Patterns: Understanding Common Architectural Styles and When to Use Them
"Software Architecture Patterns" by Mark Richards deserves to be called a long article instead of a book because it has fewer than 100 pages. Even so, it left a positive impression...
IMHO, the Event-Driven vs. Message-Driven part was the best short explanation I've ever read about this topic.
"Software Architecture Patterns: Understanding Common Architectural Styles and When to Use Them" by Mark Richards deserves to be called a long article instead of a book because it has fewer than 100 pages. Even so, it left a positive impression because the writing was nice and simple without excessive words.
The title should be "Software Architecture Styles," as Mark himself suggested, because the book talks about macro structures instead of building blocks (patterns). You find no code here but useful and easy-to-comprehend illustrations of the various styles.
The content targets technical decision-makers, such as architects and senior developers. If you are looking for a quick introduction or refresher on architectural styles, this book is a good investment of time.
The other topic covered:
- Architectural Structures and Styles
- Layered Architecture
- Microkernel Architecture
- Event-Driven Architecture
- Microservices Architecture
- Space-Based Architecture
PS: Looking forward to reading Mark's next book, "Software Architecture: The Hard Parts: Modern Trade-Off Analyses for Distributed Architectures," sometime soon since I have a copy.
Software Architecture Patterns: Understanding Common Architectural Styles and When to Use Them (Mark Richards, O'Reilly, Second Edition, 2022, 73p)