Software Architecture by Example: Using C# and .NET
Paul Michaels
Résumé
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.
- 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
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 ProblemChapter 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 ProblemChapter 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 ProblemChapter 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
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.
Caractéristiques techniques
| PAPIER | |
| Éditeur(s) | Apress |
| Auteur(s) | Paul Michaels |
| Parution | 28/04/2022 |
| Nb. de pages | 207 |
| EAN13 | 9781484279892 |
Avantages Eyrolles.com
Consultez aussi
- Les meilleures ventes en Graphisme & Photo
- Les meilleures ventes en Informatique
- Les meilleures ventes en Construction
- Les meilleures ventes en Entreprise & Droit
- Les meilleures ventes en Sciences
- Les meilleures ventes en Littérature
- Les meilleures ventes en Arts & Loisirs
- Les meilleures ventes en Vie pratique
- Les meilleures ventes en Voyage et Tourisme
- Les meilleures ventes en BD et Jeunesse
