Software Architecture by Example

Design system solutions using modern architectural patterns and practices. This book discusses methods to keep a system responsive, even when it is being constantly updated, extending a system's functionality without changing the core code, methods of maintaining data history, and designing a distributed transactional system.

This book will guide you in understanding how a software solution is designed using different architectural processes and scenarios. Each scenario explains if and why a software solution is required to resolve a given issue, and discusses possible architectural approaches to solve the problem. You will learn specific implementations of software architecture for each case along with different approaches to achieve the solutions. Each chapter is structured as a real-world requirement from a client and describes a process to meet that requirement.

After reading this book, you should have a high-level understanding of the architectural patterns used in the book, and you should have a methodology for approaching system design.

WHAT YOU WILL LEARN

* Understand design principles and considerations for various stages of software development
* Translate patterns into code samples
* Create a blueprint for approaching system design
* Understand architectural patterns: CQRS, event sourcing, distributed systems, distributed transactions, and plug-in architecture



WHO THIS BOOK IS FOR

Developers who wish to move into architecture, and junior software architects also will find the book useful

PAUL MICHAELS is the Head of Development at musicMagpie. He started his career as a professional software engineer in 1997. Paul is a regular speaker, published author, and Microsoft MVP. He enjoys programming, playing with new technology, and finding neat solutions to problems. When he's not working, you can find him cycling or walking around The Peak District, playing table tennis, or trying to cook for his wife and two children. You can follow him on twitter @paul_michaels or find him on LinkedIn. He also writes a blog at pmichaels.net.

CHAPTER 1: THE TICKET SALES PROBLEM

CHAPTER GOAL: DESIGN A SOFTWARE SOLUTION THAT ADDRESSES THE PROBLEM OF SELLING TICKETS FOR EVENTS. TICKET SALES WILL BE INITIALLY LOW, BUT FOR CERTAIN EVENTS THERE WILL BE HUGE SPIKES.

NO OF PAGES: 50

SUB -TOPICS

1. Message queues / pub / sub

2. CQRS – which it doesn’t fit

CHAPTER 2: THE CASH DESK PROBLEM

CHAPTER GOAL: DESIGN A SOLUTION THAT CATERS FOR A SYSTEM TRACKING MONEY IN AND OUT OF A CASH DESK.

NO OF PAGES: 50

SUB - TOPICS

1. Event Sourcing

2.

CHAPTER 3: THE TRAVEL AGENT PROBLEM

CHAPTER GOAL: DESIGN A SOLUTION THAT CATERS FOR A SYSTEM WHEREBY YOU NEED TO INTERFACE WITH MANY DIFFERENT THIRD-PARTY SYSTEMS AND COLLATE THE RESULTS.

NO OF PAGES: 50

SUB - TOPICS:

1. Distributed systems

2. Microservices

3. Service bus

4. Scheduler Agent Supervisor Pattern

CHAPTER 4: THE SOCIAL MEDIA PROBLEM

CHAPTER GOAL: DESIGN A SOLUTION THAT CATERS FOR A SYSTEM WHEREBY A HIGH FREQUENCY OF UPDATES ARE MADE, AND YET THE EXACT ORDER OF THE TRANSACTIONS IS UNIMPORTANT.

NO OF PAGES: 50

SUB - TOPICS:

1. CQRS

CHAPTER 5: THE ADMIN APPLICATION PROBLEM

CHAPTER GOAL: DESIGN A SOLUTION WHERE A USER IS ABLE TO CONFIGURE THE RULES WITHIN A GIVEN APPLICATION.

NO OF PAGES: 50

1. N-Tier

2. Plug-in architecture

CHAPTER 6: THE TRAVEL REP PROBLEM

CHAPTER GOAL: DESIGN A SOLUTION TO ALLOW AN APPLICATION TO ACCEPT TRAVEL AGENT QUERIES, BUT TO POLL THE SERVER OFFLINE

NO OF PAGES: 50

1. Ambassador pattern

2. Message Queues