Cantitate/Preț
Produs

Software Architecture by Example: Using C# and .NET

Autor Paul Michaels
en Limba Engleză Paperback – 29 apr 2022
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

Citește tot Restrânge

Preț: 28925 lei

Preț vechi: 36157 lei
-20% Nou

Puncte Express: 434

Preț estimativ în valută:
5536 5839$ 4626£

Carte disponibilă

Livrare economică 11-25 decembrie

Preluare comenzi: 021 569.72.76

Specificații

ISBN-13: 9781484279892
ISBN-10: 1484279891
Pagini: 207
Ilustrații: XXII, 207 p. 59 illus.
Dimensiuni: 178 x 254 x 19 mm
Greutate: 0.41 kg
Ediția:1st ed.
Editura: Apress
Colecția Apress
Locul publicării:Berkeley, CA, United States

Cuprins

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


Notă biografică

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.


Textul de pe ultima copertă

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
 
 

Caracteristici

All architectural principles and patterns are explained and translated into concrete code samples
Includes examples and code written in C# and .NET
Covers alternative solutions to each problem and scenario discussed

Descriere

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