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 arc
Table of Contents
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
