Over the past year or so, Yahoo has been working hard on redesigning some of its most popular products, such as Yahoo.com, Yahoo News, Yahoo Finance, and Yahoo Sports. As you can imagine, this is not a trivial task. These products, which have all been around for more than 10 years, are close to people’s hearts and part of the daily habits of hundreds of millions of people around the world.
There are the obvious business challenges to overcome—Yahoo runs tons of experiments to make sure KPIs, engagement metrics, revenue, etc. are all good—as well as the engineering challenges of launching products at such massive scale, which include ensuring Yahoo has sufficient capacity for breaking news events like Prince’s death or the Chinese stock market crash last year and enough capacity to handle a 10x increase in RPS to its APIs serving the Stocks native app after an iOS release. Yahoo must also be prepared for special events like the first-ever NFL livestream event on Yahoo.com, watched live by tens of millions of users, or the first-ever livestream of Berkshire Hathaway’s shareholder meeting on Yahoo Finance—not to mention the inevitable cultural challenges faced by most large companies where microcultures can exist within different business units and subteams.
So how does Yahoo succeed? Well, it’s no secret. Yahoo solves most operability problems and challenges using software; it follows a set of rigorous practices and procedures aimed at operational readiness; and it has developed a performance and operability culture within the company. At a high level, Yahoo makes sure that every product and application it builds is reliable, performs within the SLA, is fault tolerant, degrades gracefully, is highly distributed, highly decoupled, secure, and properly instrumented, and scales horizontally. The company also makes sure that most common error conditions in production are auto-remediated and that applications are continuously fault injected to test their fault tolerance and resilience. Hundreds of thousands of automated tests are run in Yahoo’s build and deploy pipelines on every commit as code is continuously deployed (no humans allowed). Of course, all products are continuously monitored and alerted upon when issues arise (alerts are routed to the teams who can actually fix the problem).
The overarching goal is product availability and performance. Yahoo obsesses over providing a great end-user experience and has a maniacal focus on performance—metrics like above-fold time (AFT) and time to first byte (TTFB) are constantly talked about in tech council meetings and also constantly monitored. Teams also use clever tactics like speculative retries (upon noticing failures) at the application level to reduce long tail, falling back to a cached version of a module on a page (module-level fallbacks) after an SLA miss; and failing safely to a cached version of a full page after an SLA miss (or timeout with the downstream)—all of which are helpful in providing an uninterrupted browsing experience even when there are errors/faults within the system.
Want to learn more? Join Kishore Jalleda and Gopal Mor as they explain how they have applied DevOps best practices at scale to successfully launch several high-profile products at Yahoo in the recent past.
Kishore Jalleda is the head of production engineering in the Americas in Yahoo’s Publisher Products Unit, which includes many popular destinations like Yahoo.com, Yahoo Finance, Yahoo Sports, and Yahoo News. Previously, Kishore was the head of SRE at Zynga and worked at IMVU, one of the pioneers of continuous delivery (with cofounder Eric Ries, the author of Lean Startup).
Gopal Mor is a software architect at Yahoo. Gopal has held various engineering roles at Yahoo. His areas of interests include performance, scalability, and resiliency. Gopal likes to tinker with Arduinos and Raspberry Pis in his spare time.
©2016, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org