Software Architecture by Example
☆☆☆☆☆
(0 reviews)
Lowest price (incl. delivery)
66,99 USD
Typical price38,15 PLN
Lowest (90 days)30,79 PLN
Offers6
Last updatedhace 1 semana
Price history (90 days)
Full history
2026-08-08
2026-08-15
| Actualizado el | Precio |
|---|---|
| 2026-08-08 | 34,99 |
| 2026-08-14 | 30,79 |
| 2026-08-15 | 38,49 |
| Vendedor | Product price | Delivery | Total | Disponibilidad | Updated | |
|---|---|---|---|---|---|---|
| SP SpringerNatureLink Shop INT | 41,99 USD | 25,00 USD | 66,99 USD | Disponible | hace 1 día | View offer |
| SP SpringerNatureLink Shop INT | 41,99 USD | 29,00 USD | 70,99 USD | Disponible | hace 1 día | View offer |
| SP SpringerNatureLink Shop INT | 45,49 USD | 25,00 USD | 70,49 USD | Disponible | hace 1 día | View offer |
| SP SpringerNatureLink Shop INT | 45,49 USD | 19,00 USD | 64,49 USD | Disponible | hace 1 día | View offer |
| SP Springer Nature Author | 45,49 USD | 15,00 USD | 60,49 USD | Disponible | hace 1 semana | View offer |
| SP SpringerNatureLink Shop INT | 44,93 EUR | 19,00 EUR | 63,93 EUR | Disponible | hace 1 día | View offer |
Los precios y la disponibilidad pueden cambiar. Última actualización: 08.08.2026 10:41.
0,0
☆☆☆☆☆
0 reviews
5★
0%
4★
0%
3★
0%
2★
0%
1★
0%
Product reviews
No reviews yet — be the first!
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