{"product_id":"138996","title":"DevOps Handbook 2\/e ","description":"\u003ccenter\u003e\u003cdiv style=\"text-align:center\"\u003e\u003cimg src=\"https:\/\/tmgdisk01.cafe24.com\/images\/vs\/4172\/sv\/3jXPeHkpLshPnniugYOqZPET1kmCyY.png?v=1765071765\" 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 DevOps Handbook 2\/e \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\/126581925\/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\n\u003ch5\u003e \u003cb\u003eBook Introduction\u003c\/b\u003e\n\u003c\/h5\u003e  \u003c\/div\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\u003cdiv\u003eDevOps is a compound word of software development and operations, and refers to an environment and culture that continuously and stably develops and operates software through communication, collaboration, and integration between software developers and information technology experts.\u003cbr\u003e Since the publication of the first edition in 2016, the second edition has been refined and supplemented based on the latest research findings, practices, and case studies.\u003cbr\u003e In today's world, where everything has changed since the COVID-19 pandemic in 2020, this book will provide insight into not only the concept of DevOps, but also its modern significance and various concepts and principles that can be applied in actual development.\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 \u003cb\u003ePart 1.\u003cbr\u003e Three ways\/\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e \u003cb\u003ePart 1 \/ Introduction\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e Chapter 1.\u003cbr\u003e Agile, Continuous Delivery, and the Three Methods \u003cbr\u003e__Manufacturing (Production) Value Stream\u003cbr\u003e __Technology Value Stream\u003cbr\u003e __Three Principles Underpinning DevOps\u003cbr\u003e ____Case Study: 2nd Edition Additional Access to Cruising Altitude:\u003cbr\u003e ____American Airlines' DevOps Journey (Part 1) (2020)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 2.\u003cbr\u003e Method 1: Flow Principle\u003cbr\u003e __Visualizing work\u003cbr\u003e __Limit Work in Progress (WIP)\u003cbr\u003e __Reducing the size of batch jobs\u003cbr\u003e __Reduce the number of handoffs\u003cbr\u003e __Continuously check and improve constraints\u003cbr\u003e __Removing pain and waste from the value stream\u003cbr\u003e ____Case Study: Managing Flow and Constraints in Healthcare, 2nd Edition (2001)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 3.\u003cbr\u003e Method Two: The Feedback Principle\u003cbr\u003e __Working safely in complex systems\u003cbr\u003e __Check the problem at the time it occurs\u003cbr\u003e __Accumulating new knowledge through swarming and problem solving\u003cbr\u003e Case Study: Pulling the Andon Code, 2nd Edition (2018)\u003cbr\u003e __Keeping quality activities closer to the source\u003cbr\u003e __Optimizing Downstream Work Centers\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 4. \u003cbr\u003eThe Third Method: The Principle of Continuous Learning and Experimentation\u003cbr\u003e __Enabling organizational learning and a safety culture\u003cbr\u003e __Institutionalize daily work improvements\u003cbr\u003e __Transform local discoveries into organization-wide improvements.\u003cbr\u003e __Add resilience patterns to your daily work\u003cbr\u003e __Leaders strengthen a learning culture.\u003cbr\u003e ____Case Study: The Bell Labs Story (1925), 2nd Edition\u003cbr\u003e __conclusion\u003cbr\u003e Part 1 \/ Conclusion\u003cbr\u003e\u003cbr\u003e \u003cb\u003ePart 2.\u003cbr\u003e Where to start?\u003cbr\u003e\u003cbr\u003e Part 2 \/ Introduction\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e Chapter 5.\u003cbr\u003e Select a value stream to start with\u003cbr\u003e __Nordstrom's DevOps Transformation\u003cbr\u003e __Greenfield Service VS.\u003cbr\u003e Brownfield Services\u003cbr\u003e ____Case Study: 2nd Edition Supplement Castle Run: Aerial Refueling Systems\u003cbr\u003e ______Brownfield Transition (2020)\u003cbr\u003e __Consider both the record system and the participation system.\u003cbr\u003e __Start with the most empathetic and innovative group.\u003cbr\u003e __Scaling DevOps across the entire organization\u003cbr\u003e ____Case Study: Scaling DevOps Across Your Business, 2nd Edition Additions:\u003cbr\u003e American Error Lines' DevOps Journey (Part 2) (2020) \u003cbr\u003e____Case Study: HMRC, 2nd Edition (Using Large-Scale PaaS)\u003cbr\u003e ______Reviving the Economy from Ruins (2020)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 6.\u003cbr\u003e Understanding and visualizing work within the value stream and extending it across the organization.\u003cbr\u003e __Nordstrom's Value Stream Mapping Experience\u003cbr\u003e Identifying the team that supports your value stream\u003cbr\u003e __Create a value stream map to understand your work.\u003cbr\u003e __Building a Dedicated Transformation Team\u003cbr\u003e ____Case Study: LinkedIn, Operation Inversion (2011)\u003cbr\u003e __Using tools to promote behavior change\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 7.\u003cbr\u003e Organizational and Architecture Design Methods Considering Conway's Law\u003cbr\u003e Conway's Law in Etsy\u003cbr\u003e __Organization's Archetype\u003cbr\u003e Problems with excessive functional orientation (cost optimization)\u003cbr\u003e __Activating a market-oriented team (optimizing for speed)\u003cbr\u003e __Creating functionally oriented tasks\u003cbr\u003e Testing, operations, and security are everyone's daily tasks.\u003cbr\u003e __Make every team member a generalist\u003cbr\u003e __Invest in services and products, not projects. \u003cbr\u003e__Design team boundaries according to Conway's Law\u003cbr\u003e __For developer productivity and safety\u003cbr\u003e ____Build a loosely coupled architecture\u003cbr\u003e __Keep your team small (the two-pizza rule)\u003cbr\u003e ____Case Study: Target, API Activation (2015)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 8.\u003cbr\u003e How to integrate daily tasks and operations to achieve optimal results\u003cbr\u003e __Big Fish Games\u003cbr\u003e __Create shared services to improve developer productivity.\u003cbr\u003e __Include operations engineers in your service team.\u003cbr\u003e __Designate an operations contact person for each service team.\u003cbr\u003e __Integrate operations into the development team's regular work activities.\u003cbr\u003e ____Case Study: 2nd Edition Supplement Nationwide Building Society,\u003cbr\u003e How to Do ______ Better (2020)\u003cbr\u003e __conclusion\u003cbr\u003e Part 2 \/ Conclusion\u003cbr\u003e\u003cbr\u003e \u003cb\u003ePart 3.\u003cbr\u003e Method 1: Technical Practices for Improving Flow\u003cbr\u003e\u003cbr\u003e Part 3 \/ Introduction\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e Chapter 9.\u003cbr\u003e Creating the foundation for a deployment pipeline\u003cbr\u003e The Enterprise Data Warehouse Story (2009)\u003cbr\u003e __Development, test, and production environments on demand \u003cbr\u003eAllow ____ to be created\u003cbr\u003e __Create a single repository for the entire system\u003cbr\u003e __Create infrastructure that is easier to rebuild than to repair.\u003cbr\u003e ____Case Study: 2nd Edition Additional Containers for $30 Billion\u003cbr\u003e Hotel companies that made ______ profits (2020)\u003cbr\u003e __Development items including execution in a similar production environment\u003cbr\u003e ____Revise the definition of 'complete'\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 10.\u003cbr\u003e Enable fast and reliable automated testing.\u003cbr\u003e __Google's Web Server Story (2005)\u003cbr\u003e __Continuously build, test, and integrate your code with your environment.\u003cbr\u003e __Create fast, reliable, and automated verification test suites.\u003cbr\u003e __Find errors in automated tests as early as possible.\u003cbr\u003e __If your deployment pipeline breaks, pull the Andon code.\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 11.\u003cbr\u003e Enable and practice continuous integration.\u003cbr\u003e __HP LaserJet Firmware (2014)\u003cbr\u003e __Small batch development and code in trunk\u003cbr\u003e __What happens when you commit rarely? \u003cbr\u003e__Apply trunk-based development practices\u003cbr\u003e ____Case Study: Bazaarvoice, Continuous Integration (2012)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 12.\u003cbr\u003e Automate and enable low-risk launches.\u003cbr\u003e __Automate the deployment process\u003cbr\u003e ____Case Study CSG International, Daily Distribution (2013)\u003cbr\u003e ____Case Study: Etsy, Self-Service Developer Deployment and Continuous Delivery (2014)\u003cbr\u003e __Separate release and distribution\u003cbr\u003e ____Case Study: Dixons Retail Deploys Blue Green Store Management System (2008)\u003cbr\u003e ____Case Study: Facebook Chat, Dark Launch (2008)\u003cbr\u003e __A Study on Continuous Delivery and Continuous Distribution\u003cbr\u003e ____Case Study: Creating a Win-Win Relationship Between Development and Operations, 2nd Edition, Additional CSG (2016)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 13.\u003cbr\u003e Architecture for low-risk releases\u003cbr\u003e __Architecture that improves productivity, testability, and safety\u003cbr\u003e __Architecture Archetypes - Monolith vs.\u003cbr\u003e Microservices\u003cbr\u003e ____Case Study: Amazon, Evolutionary Architecture (2002) \u003cbr\u003e__For the safe evolution of enterprise architecture\u003cbr\u003e Use the ____Strangler Application Pattern\u003cbr\u003e ____Case Study: The Strangler Pattern in the Blackboard Learn Project (2011)\u003cbr\u003e __conclusion\u003cbr\u003e Part 3 \/ Conclusion\u003cbr\u003e\u003cbr\u003e \u003cb\u003ePart 4.\u003cbr\u003e Method Two: Technical Practices for Feedback\u003cbr\u003e\u003cbr\u003e Part 4 \/ Introduction\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e Chapter 14.\u003cbr\u003e Generate telemetry that enables problem identification and resolution.\u003cbr\u003e __Etsy's DevOps Transformation\u003cbr\u003e __Build a centralized telemetry infrastructure\u003cbr\u003e __Generate application logging telemetry useful for production.\u003cbr\u003e __Use telemetry to guide troubleshooting\u003cbr\u003e __Enable the generation of production metrics in daily work\u003cbr\u003e __Create your own service to access telemetry and information radiators.\u003cbr\u003e ____Case Study: LinkedIn Creates Its Own Service Metrics (2011)\u003cbr\u003e __Identify and address telemetry's shortcomings.\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 15. \u003cbr\u003eAnalyze telemetry to better predict problems and achieve your goals.\u003cbr\u003e Telemetry on Netflix (2012)\u003cbr\u003e __Use the mean and standard deviation to detect potential problems.\u003cbr\u003e __Measure and warn of undesirable outcomes\u003cbr\u003e __Problems that arise when telemetry data does not follow a Gaussian distribution\u003cbr\u003e ____Case Study: Netflix, Automatic Capacity Scaling (2012)\u003cbr\u003e __Using anomaly detection techniques\u003cbr\u003e ____Case Study: Enhanced Anomaly Detection Techniques (2014)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 16.\u003cbr\u003e Enable feedback so development and operations can safely deploy code.\u003cbr\u003e __Make deployments more secure using telemetry\u003cbr\u003e __Development shares the responsibilities of operations and phaser rotation.\u003cbr\u003e __Let developers follow downstream work\u003cbr\u003e __Initially, let developers manage product services themselves.\u003cbr\u003e ____Case Study: Google, Implementation and Handoff Preparation Review (2010)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 17. \u003cbr\u003eIntegrate hypothesis-driven development and A\/B testing into your daily work.\u003cbr\u003e Intuit's Hypothesis-Driven Development (2012)\u003cbr\u003e __A Brief History of A\/B Testing\u003cbr\u003e Integrating A\/B Testing into Functional Testing\u003cbr\u003e __Integrating A\/B testing into launch\u003cbr\u003e __Integrating A\/B testing into feature planning\u003cbr\u003e ____Case Study Yahoo! Answers,\u003cbr\u003e ______Doubling Sales Through Rapid Release Cycle Experiments (2010)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 18.\u003cbr\u003e Create a review and adjustment process to improve the quality of your current work.\u003cbr\u003e __GitHub Peer Review (2011)\u003cbr\u003e __The Risks of the Change Approval Process\u003cbr\u003e Potential risks of 'excessive change control'\u003cbr\u003e ____Case Study: 2nd Edition Added Adidas,\u003cbr\u003e From the Six Eyes Principle to Launch (2020)\u003cbr\u003e __Activate coordination and planning for change\u003cbr\u003e __Enable peer review of changes\u003cbr\u003e ____Case Study: Google, Code Review (2010)\u003cbr\u003e __Potential risks of performing more manual testing and prohibiting changes \u003cbr\u003e__Enable pair programming to improve all changes.\u003cbr\u003e ____Case Study Pivotal Labs, Using Pair Programming\u003cbr\u003e Replacing a Broken Code Review Process (2011)\u003cbr\u003e __Evaluating the effectiveness of the pull request process\u003cbr\u003e __Boldly eliminate bureaucratic procedures\u003cbr\u003e __conclusion\u003cbr\u003e Part 4 \/ Conclusion\u003cbr\u003e\u003cbr\u003e \u003cb\u003ePart 5.\u003cbr\u003e The Third Way: Technical Practices for Continuous Learning and Experimentation\u003cbr\u003e\u003cbr\u003e Part 5 \/ Introduction\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e Chapter 19.\u003cbr\u003e Activate and instill learning as part of your daily routine.\u003cbr\u003e __AWS US East Region and Netflix (2011)\u003cbr\u003e __Create a fair learning culture\u003cbr\u003e __Plan a retrospective meeting after an incident.\u003cbr\u003e __Make retrospective reviews as widely public as possible.\u003cbr\u003e Reduce your tolerance for accidents to detect the weakest signals of failure.\u003cbr\u003e Redefine failure and encourage calculated risk-taking.\u003cbr\u003e __Instill resilience and learning by instilling production failures.\u003cbr\u003e __Introduce game days to practice failure. \u003cbr\u003e____Case Study: 2nd Edition Additional CSG, Disability as a Powerful Learning Opportunity\u003cbr\u003e ______Transition (2021)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 20.\u003cbr\u003e Transform local discoveries into organization-wide improvements.\u003cbr\u003e __Automate and store organizational knowledge using chat rooms and chatbots.\u003cbr\u003e __GitHub's Hubot\u003cbr\u003e __Automate the standardization process of software to enable reuse.\u003cbr\u003e __Create a single shared source code repository for the entire organization.\u003cbr\u003e __Use automated testing as a documentation and practice community to spread knowledge.\u003cbr\u003e __Systematize non-functional requirements and design operations.\u003cbr\u003e __Design for operations using coded non-functional requirements.\u003cbr\u003e __Create reusable operational user stories as development items\u003cbr\u003e __Ensure that technical choices help achieve the organization's goals.\u003cbr\u003e ____Case Study: Etsy Standardizes a New Technology Stack (2010)\u003cbr\u003e ____Case Study: 2nd Edition Additional Targets, Crowdsourcing\u003cbr\u003e ______Technology Governance (2018)\u003cbr\u003e __conclusion\u003cbr\u003e \u003cbr\u003eChapter 21.\u003cbr\u003e Make time for learning and improvement in your organization.\u003cbr\u003e __Target, 30-Day Challenge (2015)\u003cbr\u003e Pay off technical debt by institutionalizing rituals.\u003cbr\u003e __Let everyone teach and learn\u003cbr\u003e Share your experiences at the __DevOps Conference\u003cbr\u003e ____Case Study Nationwide Insurance, Capital One,\u003cbr\u003e ______Target's Internal Technology Conference (2014)\u003cbr\u003e __Create a community structure to spread the practice.\u003cbr\u003e __conclusion\u003cbr\u003e Part 5 \/ Conclusion\u003cbr\u003e\u003cbr\u003e \u003cb\u003ePart 6.\u003cbr\u003e Technical practices for integrating information security, change management, and compliance.\u003cbr\u003e\u003cbr\u003e Part 6 \/ Introduction\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e Chapter 22.\u003cbr\u003e Information security is everyone's daily job.\u003cbr\u003e __Integrate security into your development iteration demos\u003cbr\u003e __Integrate security into defect tracking and postmortems\u003cbr\u003e __Preventive security controls shared with source code repositories and\u003cbr\u003e __Integrate into shared services\u003cbr\u003e __Integrate security into your deployment pipeline\u003cbr\u003e __Ensure the security of your application \u003cbr\u003e____Case Study: Twitter, Static Security Testing (2009)\u003cbr\u003e __Ensure the security of your software supply chain\u003cbr\u003e __Ensure security for the environment\u003cbr\u003e ____Case Study 18F, Through Compliance Mercenaries\u003cbr\u003e ______Federal Government Compliance Automation\u003cbr\u003e __Integrate information security with production telemetry\u003cbr\u003e ____Case Study Etsy, Environmental Measurement (2010)\u003cbr\u003e __Protect your deployment pipeline\u003cbr\u003e ____Case Study: Shifting Left in Security, 2nd Edition, Additional Pie Mae (2020)\u003cbr\u003e __conclusion\u003cbr\u003e\u003cbr\u003e Chapter 23.\u003cbr\u003e Protecting your deployment pipeline\u003cbr\u003e __Integrate security and compliance into your change approval process.\u003cbr\u003e __Reclassify low-risk changes as standard changes\u003cbr\u003e __What to do when a change is classified as a general change\u003cbr\u003e ____Case Study Salesforce.com, Standard Changes\u003cbr\u003e ______Automated Infrastructure Change Handling (2012)\u003cbr\u003e Separate duties through code reviews \u003cbr\u003e____Case Study: Etsy, a Lesson in PCI Compliance and Segregation of Duties (2014)\u003cbr\u003e ____Case Study: Capital One, \"Fearless\" (2nd Edition)\u003cbr\u003e ______Partnership between Hyangsan Business and Development with 10 releases per day\u003cbr\u003e __Secure documentation and evidence for auditors and compliance officers.\u003cbr\u003e ____Case Study: Demonstrating Compliance in a Regulatory Environment (2015)\u003cbr\u003e ____Case Study: Production Telemetry for ATM Systems\u003cbr\u003e Depend on ______ (2013)\u003cbr\u003e __conclusion\u003cbr\u003e Part 6 \/ Conclusion\u003cbr\u003e\u003cbr\u003e Now is the Time to Act: Conclusion from the DevOps Handbook\u003cbr\u003e Concluding the 2nd edition\u003cbr\u003e supplement\u003c\/div\u003e\n\u003cdiv\u003e\u003c\/div\u003e\n\u003c\/div\u003e\n\u003cbr\u003e\u003cdiv\u003e\u003ch5\u003e \u003cb\u003ePublisher's Review\u003c\/b\u003e\n\u003c\/h5\u003e\u003c\/div\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e \u003cb\u003e◈ Target audience of this book ◈\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e This book is for all business and marketing leaders involved in technology initiatives, as well as those who perform or influence work across technology value streams (typically project management, development, QA, IT operations, and information security).\u003cbr\u003e \u003cbr\u003eReaders of this book are expected to lack extensive knowledge of domains such as DevOps, Agile, ITIL, Lean, and process improvement.\u003cbr\u003e Each topic will be introduced and explained when necessary.\u003cbr\u003e\u003cbr\u003e The purpose of this book is to create a working knowledge of the core concepts in each domain, serve as an introductory guide, introduce the language practitioners need to work with colleagues across the entire IT value stream, and create a framework of shared goals.\u003cbr\u003e It will also be valuable to business leaders and stakeholders who increasingly rely on technology organizations to achieve their goals.\u003cbr\u003e\u003cbr\u003e Furthermore, it is intended for readers in organizations that have not yet experienced all the challenges described in this book (e.g., long deployment lead times, painful deployments).\u003cbr\u003e They would benefit greatly from understanding DevOps principles, especially those related to shared goals, feedback, and continuous learning.\u003cbr\u003e \u003cbr\u003e\u003cb\u003e◈ Structure of this book ◈\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e Part 1 presents a brief history of DevOps and introduces the foundational theories and core themes gleaned from decades of relevant knowledge.\u003cbr\u003e Next, we explain the upper principles of the 'three ways': continuous learning and experimentation.\u003cbr\u003e\u003cbr\u003e Part 2 explains where and how to get started with DevOps, introducing concepts such as value streams, organizational design principles and patterns, organizational adoption patterns, and case studies.\u003cbr\u003e Part 3 explains how to build the foundation of a deployment pipeline to accelerate 'flow'.\u003cbr\u003e Learn how to implement architectures for fast and effective automated testing, continuous integration, continuous delivery, and low-risk releases.\u003cbr\u003e\u003cbr\u003e Part 4 discusses how to accelerate and amplify feedback. \u003cbr\u003eWe'll discuss how to generate effective production telemetry to discover and resolve issues, enable feedback to better predict issues and achieve goals, enable development and operations to safely deploy changes, integrate A\/B testing into daily work, and create review and adjustment processes to improve the quality of work.\u003cbr\u003e\u003cbr\u003e In Part 5, we explore how to accelerate 'continuous learning'.\u003cbr\u003e We'll show you how to establish the right culture, apply what your department learns to improve the entire organization, and properly secure time for organizational learning and improvement.\u003cbr\u003e\u003cbr\u003e Finally, Part 6 discusses how to properly integrate security compliance into your daily work. \u003cbr\u003eIt also discusses the integration of security control precautions into shared source code repositories and services, the integration of security into deployment pipelines, the enhancement of telemetry for more effective detection and recovery, and the achievement of deployment pipeline protection and change management goals.\u003cbr\u003e\u003cbr\u003e We hope that systematizing these practices will accelerate the adoption of DevOps practices, increase the success of DevOps initiatives, and reduce the effort required for DevOps transformation.\u003cbr\u003e\u003cbr\u003e \u003cb\u003e◈ Author's Note ◈\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e In 『DevOps Handbook 2\/e』, the authors have updated the text to incorporate new research, learnings, and experiences.\u003cbr\u003e You can understand DevOps as well as how DevOps is used in the industry.\u003cbr\u003e Also co-authored by renowned researcher Dr. Nicole Forsgren. \u003cbr\u003eNicole has been a great help in updating and expanding the book with new research and various indicators to support it.\u003cbr\u003e\u003cbr\u003e We also added various case studies.\u003cbr\u003e Each case study demonstrates how DevOps has spread beyond the IT department and into every industry, from the C-suite to the C-suite.\u003cbr\u003e At the end of each case study, we included one or two key takeaways highlighting the most important learnings.\u003cbr\u003e Finally, we added a conclusion to each chapter along with new resources.\u003cbr\u003e It will help you to continue learning.\u003cbr\u003e\u003cbr\u003e \u003cb\u003e◈ Translator's Note ◈\u003c\/b\u003e\u003cbr\u003e\u003cbr\u003e When I close my eyes and open them, a different world unfolds before me.\u003cbr\u003e The pace of change, especially in the software field, is faster than in any other field.\u003cbr\u003e Not only development languages, but also processes, development organizations, and development culture are all changing.\u003cbr\u003e The rapid pace of change is further accelerated by the numerous technologies being released daily.\u003cbr\u003e \u003cbr\u003eDevOps is a compound word for software development and operation, and it refers to an environment and culture that continuously and stably develops and operates software through communication, collaboration, and integration between software developers and information technology experts.\u003cbr\u003e DevOps, which focuses on a development culture based on continuous and evolving collaboration, is expanding into xOps and its impact is spreading across various areas.\u003cbr\u003e\u003cbr\u003e The DevOps Handbook 2\/e is an expanded version of the DevOps Handbook published in 2016.\u003cbr\u003e Since the publication of the first edition, the authors have refined and supplemented the content based on the latest research findings, practices, and case studies.\u003cbr\u003e In today's world, where everything has changed since the COVID-19 pandemic in 2020, this book will provide insight into not only the concept of DevOps, but also its modern significance and the various concepts and principles that can be applied in actual development. \u003cbr\u003e\n\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\"\u003eGOODS 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 issue:\u003c\/strong\u003e May 31, 2024\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 628 pages | 152*228*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 9791161758480\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 1161758488 \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":43893335228458,"sku":"138996","price":44.0,"currency_code":"EUR","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0683\/2750\/5962\/files\/155c32d8fd2a6aaf681e09ad95a52750.jpg?v=1765396894","url":"https:\/\/librairie.coreenne.fr\/en\/products\/138996","provider":"LIBRAIRIE COREENNE","version":"1.0","type":"link"}