Now that you understand what this course will cover, let's get started. In this module, you'll learn about the practice of DevOps, why Site Reliability Engineering, or SRE was developed, and who in an organization can and should apply these practices. But first, I want to tell you the story of an online retailer. Their application is similar to so many other online retailers. Customers browse the catalog, add items to their carts, and then complete their purchases. The operations team at this online retailer holds weekly reviews of key metrics. At a recent review, the team noticed that the time between the customers clicking pay and the status coming back as confirmed, was slowly increasing. They recognize that this was not a critical issue, but it did need to be addressed. The team spent some time quietly working on addressing the latency issue. Over time, on the business side of things, the product development team kept pushing features. Can you guess what happened? Well, developers started working overtime, not only to keep up with the business requests of pushing out new features, but also to resolve the small latency bug that was identified earlier. The product teams still weren't pleased with the pace of development. Basically, the IT teams put forth a heroic effort to both satisfy the business and also fix the bug. They suffer from burnout in order to meet the needs of both the business and reliability. Later, when the IT team's efforts became apparent, the product teams agreed that if they had known about the latency bug they definitely would have prioritize fixing that first before pushing new features. But because the business and IT didn't have shared standards for communication, this didn't happen. So what can you learn from this? Do you think there are ways that the business and IT can communicate better? How do you think you could achieve this in your organization? Google thought a good place to start was changing the way we think about, measure, and incentive reliability. We call this collection of principles and practices Site Reliability Engineering, or SRE. Perhaps you've heard of the DevOps movement. It is a movement that like SRE, strives to align principles, practices and incentives across teams. DevOps and SRE have a lot in common, and they're often discussed together. In fact, you may be wondering how they are different. We will explore some of the common aspects between the two, and how they complement one another in the next video.