{"product_id":"139528","title":"Site Reliability Engineering ","description":"\u003ccenter\u003e\u003cdiv style=\"text-align:center\"\u003e\u003cimg src=\"https:\/\/tmgdisk01.cafe24.com\/images\/vs\/4172\/sv\/3jXPBvegmy7pH1k0NZOBN0szZAP7ul.png?v=1765075255\" style=\"max-width:100%;max-height:10px\"\u003e\u003c\/div\u003e\u003c\/center\u003e\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\u003ccenter\u003e\n\n\u003cdiv style=\"width:95%\"\u003e\n\n\u003cdiv style=\"text-align:center;font-size:30px;font-weight:bolder;line-height:1.6em\"\u003e Site Reliability Engineering \u003c\/div\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003cdiv style=\"border-bottom:1px;border-bottom-style:dotted;border-color:;padding-bottom:20px\"\u003e\u003ccenter\u003e\u003ctable align=\"center\" width=\"100%\"\u003e\u003ctbody style=\"border:0px\"\u003e\n\n\u003ctr\u003e\u003ctd align=\"center\" style=\"line-height:1.2em;text-align:center;font-size:18px;color:black;font-weight:bold;padding-bottom:20px;\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\n\n\u003ctr\u003e\u003ctd style=\"text-align:center\"\u003e\u003cimg src=\"https:\/\/image.yes24.com\/goods\/57979286\/XL\" style=\"max-width:100%;height:auto\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\n\n\n\u003c\/tbody\u003e\u003c\/table\u003e\u003c\/center\u003e\u003c\/div\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003cdiv style=\"width:95%;{split_style6}padding-top:20px;padding-bottom:20px\"\u003e\n\n\u003cdiv style=\"text-align:left;font-size:16px;font-weight:bold;padding-bottom:20px\"\u003e Description \u003c\/div\u003e\n\n\u003cdiv style=\"text-align:left;word-break:break-all;font-size:14px;line-height:1.6em;\"\u003e\n\n\u003cdiv\u003e\u003ch5\u003e \u003cb\u003eBook Introduction\u003c\/b\u003e\n\u003c\/h5\u003e\u003c\/div\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\u003cdiv\u003e \u003cb\u003eA book full of inspiration to help you grow to the next level!\u003cbr\u003e Experience Google's principle that code that actually works is the most important!\u003cbr\u003e\u003c\/b\u003e\u003cbr\u003e The lifespan of a software system is usually determined by the period during which it is actually used, not by its design or implementation phase.\u003cbr\u003e So why have software engineers considered the process of designing and implementing large-scale computing systems to be of the utmost importance?\u003cbr\u003e\u003cbr\u003e In this book, core members of Google's Site Reliability Engineering team share, through essays and editorials, how and why they implement, deploy, monitor, and maintain the world's largest software system by focusing on the entire software lifecycle. \u003cbr\u003eThis will allow you to apply the principles and practices that enabled Google engineers to build more scalable, reliable, and effective systems to your own organization.\u003cbr\u003e\u003cbr\u003e Main contents of this book\u003cbr\u003e *Introduction: Introduces what site reliability engineering is and how it differs from traditional IT practices.\u003cbr\u003e *Principles: Introduces patterns, behaviors, and various issues that affect the work of site reliability engineers.\u003cbr\u003e *Case Study: Learn the theory and case studies for building and operating large-scale distributed computing systems, which is part of SRE's daily work.\u003cbr\u003e *Management: Explore ways to apply Google's recommended new hire training, communication, and meeting management practices to your own organization.\u003cbr\u003e\u003cbr\u003e\n\u003c\/div\u003e\u003c\/div\u003e\n\u003cdiv\u003e\u003cul\u003e\u003cli\u003e You can preview some of the book's contents.\u003cbr\u003e \u003cspan\u003ePreview\u003c\/span\u003e\n\n\u003c\/li\u003e\u003c\/ul\u003e\u003c\/div\u003e\n\u003c\/div\u003e\n\u003cbr\u003e\u003cdiv\u003e\u003ch5\u003e \u003cb\u003eindex\u003c\/b\u003e\n\u003c\/h5\u003e\u003c\/div\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e PART I INTRODUCTION\u003cbr\u003e CHAPTER 01 Introduction _ 3 \u003cbr\u003eHow to Use System Administrators for Service Management _ 3\u003cbr\u003e Google's Solution to Service Management: Site Reliability Engineering _ 5\u003cbr\u003e SRE's Creed _ 8\u003cbr\u003e In conclusion _ 14\u003cbr\u003e\u003cbr\u003e CHAPTER 02 Google's Production Environment from an SRE Perspective 15\u003cbr\u003e Hardware _ 15\u003cbr\u003e System software that 'tunes' the hardware _ 17\u003cbr\u003e Other System Software _ 21\u003cbr\u003e Software Infrastructure _ 22\u003cbr\u003e Development Environment _ 23\u003cbr\u003e Shakespeare: Example Service _ 24\u003cbr\u003e\u003cbr\u003e PART II PRINCIPLES AND RULES\u003cbr\u003e CHAPTER 03 Accepting Risks _ 30\u003cbr\u003e Managing Risk Factors _ 31\u003cbr\u003e Measuring Service Risk _ 32\u003cbr\u003e Service Risk Acceptance _ 34\u003cbr\u003e Using the Error Budget _ 40\u003cbr\u003e\u003cbr\u003e CHAPTER 04 Service Level Objectives _ 44\u003cbr\u003e Service Level Related Terminology _ 45\u003cbr\u003e Indicator Settings _ 48\u003cbr\u003e Goal Setting Exercise _ 51\u003cbr\u003e Practice on the Agreement _ 56\u003cbr\u003e\u003cbr\u003e CHAPTER 05 No More Digging! _ 57\u003cbr\u003e The Definition of Digging _ 58\u003cbr\u003e Reasons Why Less Digging is Good _ 60\u003cbr\u003e What kind of work falls under engineering? _ 61 \u003cbr\u003eIs digging always a bad thing? _ 62\u003cbr\u003e Conclusion _ 63\u003cbr\u003e\u003cbr\u003e CHAPTER 06 Distributed System Monitoring _ 64\u003cbr\u003e Definition _ 64\u003cbr\u003e Why Monitor? _ 66\u003cbr\u003e Setting Appropriate Expectations for Monitoring _ 67\u003cbr\u003e Symptoms and Causes _ 68\u003cbr\u003e Black Box and White Box _ 69\u003cbr\u003e Four Crucial Indicators _ 70\u003cbr\u003e Considerations for the last request (or execution and performance) _ 72\u003cbr\u003e Choosing the Right Measurement Method _ 72\u003cbr\u003e Not simpler, but as simple as possible _ 73\u003cbr\u003e Combining the principles we've discussed so far _ 74\u003cbr\u003e Long-term monitoring _ 76\u003cbr\u003e Conclusion _ 78\u003cbr\u003e\u003cbr\u003e CHAPTER 07 Google's Advanced Automation _ 80\u003cbr\u003e The Value of Automation _ 81\u003cbr\u003e The Value of Google SRE _ 83\u003cbr\u003e Automation Case Study _ 85\u003cbr\u003e Do Yourself a favor: Automate Everything! _ 88\u003cbr\u003e A Move of God: Automating Cluster Turn-Ups _ 91\u003cbr\u003e Vogue: The Birth of a Warehouse-Sized Computer _ 98\u003cbr\u003e Reliability is a fundamental function _ 101\u003cbr\u003e Recommendations _ 101\u003cbr\u003e\u003cbr\u003e CHAPTER 08 Release Engineering _ 103\u003cbr\u003e The Role of a Release Engineer _ 104\u003cbr\u003e The Philosophy of Release Engineering _ 104 \u003cbr\u003eContinuous Build and Deployment _ 106\u003cbr\u003e Configuration Management Techniques _ 111\u003cbr\u003e Conclusion _ 112\u003cbr\u003e\u003cbr\u003e CHAPTER 09 Conciseness _ 114\u003cbr\u003e System stability vs.\u003cbr\u003e Swiftness _ 115\u003cbr\u003e The Virtue of Boredom _ 115\u003cbr\u003e My code will never give up! _ 116\u003cbr\u003e Indicator of 'Negative Impact Code' _ 116\u003cbr\u003e Minimal API _ 117\u003cbr\u003e Modularization _ 117\u003cbr\u003e Simplifying Releases _ 118\u003cbr\u003e Concise Conclusion _ 119\u003cbr\u003e\u003cbr\u003e PART III CASE\u003cbr\u003e CHAPTER 10 Practical Reminders for Time Series Data _ 127\u003cbr\u003e The Birth of Borgmon _ 128\u003cbr\u003e Manipulating the Application _ 130\u003cbr\u003e Collection of exported data _ 131\u003cbr\u003e Storage for Time Series Data _ 132\u003cbr\u003e Evaluation of Rules _ 135\u003cbr\u003e Notification _ 140\u003cbr\u003e Sharding in Monitoring Topologies _ 141\u003cbr\u003e Black Box Monitoring _ 142\u003cbr\u003e Maintaining Settings _ 143\u003cbr\u003e Over the past 10 years… _ 145\u003cbr\u003e\u003cbr\u003e CHAPTER 11 Emergency Standby _ 146\u003cbr\u003e Introduction _ 146\u003cbr\u003e The Life of an Emergency Response Engineer _ 147\u003cbr\u003e Balancing Emergency Standby Work _ 148\u003cbr\u003e Considering Safety _ 150\u003cbr\u003e Escape from Inappropriate Operating Loads _ 153\u003cbr\u003e Conclusion _ 155\u003cbr\u003e\u003cbr\u003e CHAPTER 12 Effective Failover _ 156\u003cbr\u003e Theory _ 157 \u003cbr\u003eLet's get into the real world _ 159\u003cbr\u003e The Magic of Negative Results _ 168\u003cbr\u003e Case Study _ 171\u003cbr\u003e Making Handling Disabilities a Little Easier _ 175\u003cbr\u003e Conclusion _ 176\u003cbr\u003e\u003cbr\u003e CHAPTER 13 EMERGENCY RESPONSE _ 177\u003cbr\u003e What should I do if something goes wrong with my system? _ 178\u003cbr\u003e Test-induced failures _ 178\u003cbr\u003e Disability due to change _ 180\u003cbr\u003e Procedural Obstacles _ 183\u003cbr\u003e All problems solved _ 186\u003cbr\u003e Learn from the past.\u003cbr\u003e And don't repeat _ 186\u003cbr\u003e Conclusion _ 188\u003cbr\u003e\u003cbr\u003e CHAPTER 14 MANAGING DISABILITIES _ 189\u003cbr\u003e Inadequate Disability Management _ 190\u003cbr\u003e A Detailed Analysis of Inadequate Handling of Disabilities _ 191\u003cbr\u003e Fundamentals of Disability Management Procedures _ 191\u003cbr\u003e Properly Managed Failover _ 194\u003cbr\u003e When to declare a disability? _ 195\u003cbr\u003e Summary _ 196\u003cbr\u003e\u003cbr\u003e CHAPTER 15 Postmortem Culture: Learning from Failure _ 197\u003cbr\u003e Google's Postmortem Philosophy _ 198\u003cbr\u003e Collaboration and Knowledge Sharing _ 200\u003cbr\u003e Introducing Postmortem Culture _ 201\u003cbr\u003e Conclusion and Continuous Improvement _ 204\u003cbr\u003e\u003cbr\u003e CHAPTER 16 TRACING SYSTEM OUTAGES _ 205\u003cbr\u003e Escalator _ 206\u003cbr\u003e Outerator _ 206\u003cbr\u003e \u003cbr\u003eCHAPTER 17 Testing for Reliability _ 212\u003cbr\u003e Types of Software Testing _ 214\u003cbr\u003e Configuring the Test and Build Environment _ 221\u003cbr\u003e Testing in Large-Scale Environments _ 223\u003cbr\u003e Conclusion _ 237\u003cbr\u003e\u003cbr\u003e CHAPTER 18 Software Engineering in SRE Organizations _ 238\u003cbr\u003e Why Software Engineering Capabilities Matter in SRE Organizations _ 239\u003cbr\u003e Auxon Case Study: Project Background and Where the Problems Arrived _ 240\u003cbr\u003e Intent-Based Capacity Planning _ 244\u003cbr\u003e How to Foster Software Engineering in Your SRE Organization _ 254\u003cbr\u003e Conclusion _ 259\u003cbr\u003e\u003cbr\u003e CHAPTER 19 Front-End Load Balancing _ 260\u003cbr\u003e Not everything can be solved by force alone _ 260\u003cbr\u003e Load Balancing Using DNS _ 262\u003cbr\u003e Load Balancing Using Virtual IP Addresses _ 265\u003cbr\u003e\u003cbr\u003e CHAPTER 20 Load Balancing in Data Centers _ 268\u003cbr\u003e Ideal Case _ 269\u003cbr\u003e Distinguishing Bad Tasks: Flow Control and Lame Ducks _ 271\u003cbr\u003e Limiting the Connection Pool Using Subsets _ 273\u003cbr\u003e Load Balancing Policy _ 280\u003cbr\u003e\u003cbr\u003e CHAPTER 21 Handling Overload _ 287 \u003cbr\u003eThe Pitfalls of 'Query Per Second' _ 288\u003cbr\u003e Per-user limits _ 289\u003cbr\u003e Client-side usage limits _ 290\u003cbr\u003e Importance _ 292\u003cbr\u003e Signals of Utilization _ 294\u003cbr\u003e Handling Overload Errors _ 295\u003cbr\u003e Load on connection _ 299\u003cbr\u003e Conclusion _ 300\u003cbr\u003e\u003cbr\u003e CHAPTER 22 Handling Continuous Failures _ 302\u003cbr\u003e Causes of Continuous Disability and Countermeasures _ 303\u003cbr\u003e Preventing Server Overload _ 309\u003cbr\u003e Slow Start and Cold Caching _ 320\u003cbr\u003e Causes of continuous disability _ 323\u003cbr\u003e Testing for Continuous Failures _ 325\u003cbr\u003e Immediate Response to Continuous Failures _ 328\u003cbr\u003e In conclusion _ 331\u003cbr\u003e\u003cbr\u003e CHAPTER 23 Managing Critical States: Agreeing on Distributed Reliability _ 332\u003cbr\u003e Why Consensus Is Necessary: ​​Failures in Collaboration Across Distributed Systems _ 335\u003cbr\u003e How Consensus on Distributed Blockchain Works _ 337\u003cbr\u003e System Architecture Patterns for Distributed Consensus _ 339\u003cbr\u003e Performance of Distributed Consensus _ 345\u003cbr\u003e Deploying a Distributed Consensus-Based System _ 354\u003cbr\u003e Distributed Consensus System Monitoring _ 364\u003cbr\u003e Conclusion _ 365\u003cbr\u003e \u003cbr\u003eCHAPTER 24 Distributed Periodic Scheduling with Cron _ 366\u003cbr\u003e Cron_367\u003cbr\u003e Cron Jobs and Idempotence _ 368\u003cbr\u003e Cron in Large Systems _ 369\u003cbr\u003e Cron Service Implemented by Google _ 371\u003cbr\u003e Summary _ 379\u003cbr\u003e\u003cbr\u003e CHAPTER 25 DATA PROCESSING PIPELINE _ 380\u003cbr\u003e The Origins of the Pipeline Design Pattern _ 380\u003cbr\u003e The Basic Effects of Big Data Using a Simple Pipeline Pattern _ 381\u003cbr\u003e Challenges of the Regular Pipeline Pattern _ 381\u003cbr\u003e Problems arising from unbalanced distribution of work _ 382\u003cbr\u003e Drawbacks of Regular Pipelines in Distributed Environments _ 383\u003cbr\u003e Introducing Google Workflow _ 387\u003cbr\u003e Workflow Execution Steps _ 389\u003cbr\u003e Ensuring Business Sustainability _ 391\u003cbr\u003e Summary _ 392\u003cbr\u003e\u003cbr\u003e CHAPTER 26 DATA INTEGRITY: I MUST BE READY TO READ WHAT I WRITE _ 394\u003cbr\u003e Critical Conditions for Data Integrity _ 395\u003cbr\u003e Google SRE's Goals for Maintaining Data Integrity and Availability _ 401\u003cbr\u003e How Google Solves Data Integrity Problems _ 406\u003cbr\u003e Case Study _ 419 \u003cbr\u003eGeneral Principles of SRE Related to Data Integrity _ 427\u003cbr\u003e Conclusion _ 429\u003cbr\u003e\u003cbr\u003e CHAPTER 27: Delivering Reliable Products in High-Volume Environments _ 430\u003cbr\u003e Release Coordination Engineering _ 432\u003cbr\u003e Establishing a Launch Procedure _ 434\u003cbr\u003e Developing a Launch Checklist _ 438\u003cbr\u003e Techniques for a Stable Release _ 443\u003cbr\u003e LCE's Development Capabilities _ 448\u003cbr\u003e Conclusion _ 452\u003cbr\u003e\u003cbr\u003e PART IV MANAGEMENT\u003cbr\u003e CHAPTER 28: Fostering SRE Growth Beyond Emergency Standby _ 456\u003cbr\u003e Hired a new SRE.\u003cbr\u003e What should I do now? _ 456\u003cbr\u003e First Learning Experience: A Case Study of Structure to Prevent Confusion _ 459\u003cbr\u003e Raising Star Reverse Engineers and Improvisational Thinkers _ 463\u003cbr\u003e Five Principles for Aspiring Emergency Response Engineers _ 467\u003cbr\u003e Beyond Emergency Standby: Rites of Passage and Practices of Continuous Learning _ 473\u003cbr\u003e In conclusion _ 474\u003cbr\u003e\u003cbr\u003e CHAPTER 29 Dealing with Distractions _ 475\u003cbr\u003e Managing Operational Workloads _ 476\u003cbr\u003e Factors for Determining How to Manage Distractions _ 477\u003cbr\u003e Imperfect Machine _ 478\u003cbr\u003e \u003cbr\u003eCHAPTER 30: Freeing Yourself from the Burden of Operational Tasks with SRE _ 486\u003cbr\u003e Step 1: Learn about the service and understand the context _ 487\u003cbr\u003e Step 2: Sharing Context _ 489\u003cbr\u003e Step 3: Leading the Change _ 491\u003cbr\u003e Conclusion _ 494\u003cbr\u003e\u003cbr\u003e CHAPTER 31 Communication and Collaboration in SRE _ 495\u003cbr\u003e Communication: Operational Environment Meeting _ 497\u003cbr\u003e Collaborating with SREs _ 501\u003cbr\u003e A Case Study on Collaboration in SRE: Viceroy _ 503\u003cbr\u003e Collaboration with Organizations Outside of SRE _ 509\u003cbr\u003e Case Study: DFP's Migration to F1 _ 510\u003cbr\u003e Conclusion _ 512\u003cbr\u003e\u003cbr\u003e CHAPTER 32 Improving the SRE Participation Model _ 513\u003cbr\u003e Introducing SRE: What It Is, How It Works, and Why It Works _ 513\u003cbr\u003e PRR Model _ 514\u003cbr\u003e SRE Introduction Model _ 515\u003cbr\u003e Reviewing the Operational Environment Readiness: A Simple PRR Model _ 517\u003cbr\u003e Evolution of a Simple PRR Model: Early Engagement _ 521\u003cbr\u003e Improving Service Development: Frameworks and SRE Platforms _ 524\u003cbr\u003e Conclusion _ 529\u003cbr\u003e\u003cbr\u003e PART V CONCLUSION\u003cbr\u003e CHAPTER 33 Lessons from Other Industries _ 533\u003cbr\u003e Introduction to Industry Experts _ 534\u003cbr\u003e Preparation and Disaster Testing _ 536\u003cbr\u003e Postmortem Culture _ 540 \u003cbr\u003eEliminate repetitive tasks and operational overhead through automation _ 542\u003cbr\u003e Structured and Rational Decision Making _ 544\u003cbr\u003e Conclusion _ 546\u003cbr\u003e\u003cbr\u003e CHAPTER 34 Conclusion _ 547\u003cbr\u003e\u003cbr\u003e APPENDIX.\u003cbr\u003e supplement\u003cbr\u003e APPENDIX A Availability Table _ 551\u003cbr\u003e APPENDIX B Collection of Recommended Practices for Operational Services _ 553\u003cbr\u003e\u003cbr\u003e APPENDIX C Example of a Failure Status Document _ 559\u003cbr\u003e APPENDIX D Postmortem Examples _ 561\u003cbr\u003e APPENDIX E Launch Coordination Checklist _ 566\u003cbr\u003e APPENDIX F Example of a Product Meeting _ 569\u003cbr\u003e\u003cbr\u003e References _ 573\u003cbr\u003e Search _ 584\u003cbr\u003e\n\u003c\/div\u003e\n\u003cdiv\u003e\u003c\/div\u003e\n\u003c\/div\u003e\n\u003cbr\u003e\u003cdiv\u003e\u003ch5\u003e \u003cb\u003eInto the book\u003c\/b\u003e\n\u003c\/h5\u003e\u003c\/div\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e Beyond that, the belief and talent for solving complex problems through software system development were cited as essential qualities for SREs. Within the SRE team, we closely tracked the development of these two groups' work capabilities, and to date, we have found no significant differences in the performance of these two groups of engineers. \u003cbr\u003eIn fact, the SRE team's background differences often led to the creation of unique, high-quality systems that integrated multiple technologies.\u003cbr\u003e --- p.6\u003cbr\u003e\u003cbr\u003e Understanding how well your system is meeting expectations helps you decide whether to invest in making it faster, more available, and more resilient.\u003cbr\u003e Alternatively, if the system is working well, the staff's time can be allocated to higher-priority tasks, such as addressing technical debt, adding new features, or developing other products.\u003cbr\u003e --- p.56\u003cbr\u003e\u003cbr\u003e The system has inertia.\u003cbr\u003e We found that a computer system that is functioning properly tends to continue to function until an external factor, such as a change in configuration or a change in the type of service load, occurs. \u003cbr\u003eSo the best place to start figuring out what's going wrong is the most recent change.\u003cbr\u003e --- p.165\u003cbr\u003e\u003cbr\u003e A reasonable way to implement a subset selection algorithm is to have each client randomly shuffle the list of backends, then select the backends that are accessible and in good condition to build a subset.\u003cbr\u003e The method of randomly shuffling and then selecting backends sequentially allows us to explicitly limit the number of backends to be considered, thus handling restarts and failures reliably (e.g. while maintaining a relatively small number of connections).\u003cbr\u003e However, we have experienced that this strategy does not work as desired in most cases because the load is not distributed evenly.\u003cbr\u003e --- p.275\u003cbr\u003e \u003cbr\u003eCompanies that are growing rapidly and have a high rate of change in their products and services may benefit from introducing a release orchestration engineering role.\u003cbr\u003e Such teams are especially useful when a company plans to hire more than twice as many product developers every year or two, when a service must scale to millions of users, or when stability is more important to users despite a high rate of change.\u003c\/div\u003e\n\u003cdiv\u003e --- p.452 \u003c\/div\u003e\n\u003c\/div\u003e\n\u003cdiv\u003e\u003c\/div\u003e\n\u003c\/div\u003e\n\u003c\/div\u003e\n\n\n\u003c\/div\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003cdiv style=\"width:95%;padding-top:20px;padding-bottom:20px\"\u003e\n\n\u003cdiv style=\"text-align:left;font-size:16px;font-weight:bold;padding-bottom:20px\"\u003e GOODS SPECIFICS \u003c\/div\u003e\n\n\u003cdiv style=\"text-align:left;font-size:14px;line-height:1.6em;\"\u003e\n\n\u003cdiv style=\"width:100%;margin-bottom:5px;line-height:1.6em;font-size:14px\"\u003e - \u003cstrong\u003eDate of publication:\u003c\/strong\u003e January 18, 2018\u003c\/div\u003e\n\n\u003cdiv style=\"width:100%;margin-bottom:5px;line-height:1.6em;font-size:14px\"\u003e - \u003cstrong\u003ePage count, weight, size:\u003c\/strong\u003e 624 pages | 188*245*29mm\u003c\/div\u003e\n\n\u003cdiv style=\"width:100%;margin-bottom:5px;line-height:1.6em;font-size:14px\"\u003e - \u003cstrong\u003eISBN13:\u003c\/strong\u003e 9791188621088\u003c\/div\u003e\n\n\u003cdiv style=\"width:100%;margin-bottom:5px;line-height:1.6em;font-size:14px\"\u003e - \u003cstrong\u003eISBN10:\u003c\/strong\u003e 1188621084 \u003c\/div\u003e\n\n\n\u003c\/div\u003e\n\n\n\u003c\/div\u003e\n\n\n\u003c\/div\u003e\n\n\u003ccenter\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003ccenter\u003e\u003ctable\u003e\u003ctr\u003e\u003ctd style=\"height:10px\"\u003e\u003c\/td\u003e\u003c\/tr\u003e\u003c\/table\u003e\u003c\/center\u003e\n\n\u003cspan\u003e\u003c\/span\u003e\n\n\u003c\/center\u003e\n\n\n\u003c\/center\u003e","brand":"LIBRAIRIE COREENNE","offers":[{"title":"Default Title","offer_id":43893363408938,"sku":"139528","price":45.0,"currency_code":"EUR","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0683\/2750\/5962\/files\/45a711d4e8f32bec01537363fa715c7c.jpg?v=1765398464","url":"https:\/\/librairie.coreenne.fr\/en\/products\/139528","provider":"LIBRAIRIE COREENNE","version":"1.0","type":"link"}