Software Architecture: The Hard Parts: Modern Trade-Off Analyses for Distributed Architectures

Software Architecture: The Hard Parts: Modern Trade-Off Analyses for Distributed Architectures

Taschenbuch
5.02

Durch das Verwenden dieser Links unterstützt du READO. Wir erhalten eine Vermittlungsprovision, ohne dass dir zusätzliche Kosten entstehen.

Beschreibung

There are no easy decisions in software architecture. Instead, there are many hard parts--difficult problems or issues with no best practices--that force you to choose among various compromises. With this book, you'll learn how to think critically about the trade-offs involved with distributed architectures.
Architecture veterans and practicing consultants Neal Ford, Mark Richards, Pramod Sadalage, and Zhamak Dehghani discuss strategies for choosing an appropriate architecture. By interweaving a story about a fictional group of technology professionals--the Sysops Squad--they examine everything from how to determine service granularity, manage workflows and orchestration, manage and decouple contracts, and manage distributed transactions to how to optimize operational characteristics, such as scalability, elasticity, and performance.
By focusing on commonly asked questions, this book provides techniques to help you discover and weigh the trade-offs as you confront the issues you face as an architect. Analyze trade-offs and effectively document your decisions Make better decisions regarding service granularity Understand the complexities of breaking apart monolithic applications Manage and decouple contracts between services Handle data in a highly distributed architecture Learn patterns to manage workflow and transactions when breaking apart applications
Haupt-Genre
N/A
Sub-Genre
N/A
Format
Taschenbuch
Seitenzahl
459
Preis
59.99 €

Beiträge

1
Alle
5

This book demonstrates how decisions in architecture should be made - if at all. Chapters usually start with some kind of scenario and a given problem. Then different solutions to the problem are presented, followed by details about the trade-offs. And when the decision has been made it is documented in an ADR. Besides that, it contains the usual things you can find in a book about architecture like microservices yes/no, big ball of mud yes/no and so on.

Beitrag erstellen