04796nam a22004935i 4500 979-8-8688-0288-1 DE-He213 20251030112241.0 cr nn 008mamaa 240529s2024 xxu| s |||| 0|eng d 9798868802881 979-8-8688-0288-1 10.1007/979-8-8688-0288-1 doi QA76.758 UMZ bicssc COM051230 bisacsh UMZ thema Perry, Michael L. author. aut http://id.loc.gov/vocabulary/relators/aut 77772 The Art of Immutable Architecture [electronic resource] : Theory and Practice of Data Management in Distributed Systems / by Michael L. Perry. 2nd ed. 2024. Berkeley, CA : Apress : Imprint: Apress, 2024. XXVI, 480 p. 203 illus. online resource. text txt rdacontent computer c rdamedia online resource cr rdacarrier text file PDF rda Part I: Definition -- Chapter 1: Why Immutable Architecture? -- Chapter 2: Forms of Immutable Architecture -- Chapter 3: How to Read an Historical Model -- Part II: Application -- Chapter 4: Analysis -- Chapter 5: Location Independence -- Chapter 6: Immutable Runtimes -- Chapter 7: Structural Patterns -- Chapter 8: State Transitions -- Chapter 9: Security -- Part III: Implementation -- Chapter 10: SQL Databases -- Chapter 11: Communication -- Chapter 12: Feeds -- Chapter13: Inversion. This book teaches you how to evaluate a distributed system from the perspective of immutable objects. You will understand the problems in existing designs, know how to make small modifications to correct those problems, and learn to apply the principles of immutable architecture to your tools. Most software components focus on the state of objects. They store the current state of a row in a relational database. They track changes to state over time, making several basic assumptions: there is a single latest version of each object, the state of an object changes sequentially, and a system of record exists. This is a challenge when it comes to building distributed systems. Whether dealing with autonomous microservices or disconnected mobile apps, many of the problems we try to solve come down to synchronizing an ever-changing state between isolated components. Distributed systems would be a lot easier to build if objects could notchange. After reading The Art of Immutable Architecture, you will come away with an understanding of the benefits of using immutable objects in your own distributed systems. You will learn a set of rules for identifying and exchanging immutable objects, and see a collection of useful theorems that emerges and ensures that the distributed systems you build are eventually consistent. Using patterns, you will find where the truth converges, see how changes are associative, rather than sequential, and come to feel comfortable understanding that there is no longer a single source of truth. Practical hands-on examples reinforce how to build software using the described patterns, techniques, and tools. By the end of the book, you will possess the language and resources needed to analyze and construct distributed systems with confidence. The assumptions of the past were sufficient for building single-user, single-computer systems. But as we expand to multiple devices, shared experiences, and cloud computing, they work against us. It is time for a new set of assumptions. Start with immutable objects, and build better distributed systems. What You Will Learn Evaluate a distributed system from the perspective of immutable objects Recognize the problems in existing designs, and make small modifications to correct them Start a new system from scratch, applying patterns Apply the principles of immutable architecture to your tools, including SQL databases, message queues, and the network protocols that you already use Discover new tools that natively apply these principles . Software engineering. 33953 Computer programming. Software Engineering. 33953 Programming Techniques. 65517 SpringerLink (Online service) Springer Nature eBook Printed edition: 9798868802874 Printed edition: 9798868802898 Printed edition: 9798868805677 https://doi.org/10.1007/979-8-8688-0288-1 ZDB-2-CWD ZDB-2-SXPC 60263 60263