Welcome!

Microservices Expo Authors: Kelly Burford, Derek Weeks, Elizabeth White, Liz McMillan, John Katrick

Related Topics: Microservices Expo, Open Source Cloud, @CloudExpo

Microservices Expo: Blog Feed Post

Why You Can’t Talk About Microservices Without Mentioning Netflix | @CloudExpo #API #Microservices

Netflix is one of the earliest adopters of microservices

Why You Can't Talk About Microservices Without Mentioning Netflix
by Daniel Giordano

About six years ago, Netflix began the move from a monolithic to cloud-based microservices architecture, openly documenting the journey along the way. Netflix is one of the earliest adopters of microservices, a term that didn't even exist when Netflix began moving away from its monolith. Today, the Netflix application is powered by an architecture featuring an API Gateway that handles about two billion API edge requests every day which are handled by approximately 500+ microservices. Netflix has been so successful with its architecture, that the company has open sourced a great deal of its platform including the technologies powering its microservices. Netflix has become one of the most well-known examples of a modern microservices architecture; if an article mentions microservices, odds are, it also mentions Netflix.

Caption: Netflix needed to move to an architecture that could handle the growing number of users and devices connecting to its platform. - Image Credit: Netflix.

Netflix needed to move to an architecture that could handle the growing number of users and devices connecting to its platform. - Image Credit: Netflix.

Netflix Moves to the Cloud
Netflix began moving from a monolithic to AWS cloud-based microservices architecture in 2009, long before the term microservices even existed. Netflix first began with moving movie encoding, a non-customer facing application. In 2010, Netflix began moving customer facing pieces of the website to AWS including account sign up, movie selections, TV selections, metadata, and device configuration. By the end of 2010, the entire customer facing website had been moved to AWS. By December 2011, Netflix had successfully moved to the cloud, breaking up their monolith into hundreds of fine-grained microservices.

About Microservices
The term microservices was coined by a group of software architects in 2012 but didn't start gaining in popularity until 2014, when software developer and author Martin Fowler began using the term in some of his publications.

Netflix trends

Microservices - Google Search Interest Over Time - Data Source: Google Trends

Adrian Cockcroft, a technology fellow at Battery Ventures, is well known for his role as cloud architect at Netflix where he often gave presentations about Netflix's move to the cloud and microservices. Cockcroft has developed his own definition for microservices:  "Loosely coupled service oriented architecture with bounded contexts."

Reasons for the Move
There were a number of reasons Netflix made the decision to move from a monolithic datacenter to a cloud-based microservices architecture. The primary reasons for the move, however, had to do with availability, scale, and speed. The company needed an architecture that allowed Netflix to be up and running 24/7, scale to the next order of magnitude, and be optimized for speed.

Back in 2008, when Netflix was still operating as a monolith, a single missing semicolon brought down the entire Netflix website for several hours. Monoliths tend to become spaghetti code with various components linked together and tightly coupled together. As a monolith, when something was broken in the code, all Netflix engineers had to be alerted to check and see if it was their code that had caused the problem. While it is still possible to have outages with a microservices architecture due to code errors and other issues, outages can be minimized since the platform is divided into separate services that are loosely coupled. A well-designed microservices architecture allows for better availability.

Another reason for the move to a cloud-based microservices architecture had to do with scale. Netflix was unable to build data centers fast enough to keep up with its growth rate. Not only was the number of Netflix users growing very rapidly, Netflix was also branching out to platforms like Xbox, Wii, mobile, and was expanding globally. Thousands of server instances can be commissioned simultaneously if needed to meet increased demand for services. Netflix is able to increase or decrease its capacity in minutes with AWS cloud. In the past, increasing capacity of the datacenter could take hours or days.  Scale is also undifferentiated for a monolithic application; it doesn't allow for different components to scale at different rates. For example, a customer service application could not be scaled at a different rate than a product catalog. However, this is possible with a cloud-based microservices architecture.

The microservices architecture allowed Netflix to greatly speed up development and deployment of its platform and services. The company was able to build and test global services on a large scale without impacting the current system and they could quickly roll back if there were problems. The microservices architecture also allowed Netflix to create about 30+ independent engineering teams that could work on different release schedules, which helped increase the agility and productivity of the development process.

There Were a Few Problems
While the Netflix platform is one of the best examples of a modern cloud-based microservices architecture, the move from monolith to microservices was not without some problems. When Netflix first moved the customer-facing website to the cloud, there were a lot of latency issues with the web pages. One of the ways Netflix dealt with this issue was by managing resources within AWS to avoid co-tenancy and adjust to AWS networking, which has more variable latency than the Netflix datacenters.

In April 2011, there was an outage in AWS US-East that brought down several popular websites hosted on AWS. While Netflix did not experience any large external outages because of the AWS issue, the company did have to make manual changes to its AWS configuration, moving sets of services out of Amazon's Availability Zone (AZ). The company has since automated much of the process, so that failures of this nature are handled without requiring a lot of manual intervention by Netflix engineers.

Netflix faced a number of issues as it steadily moved to a cloud-based architecture such as load increases, instance failures, zone/region failures, and performance problems. Netflix has built many technologies and tools to help address and solve these issues.

Netflix Provides Open Source Software
Netflix has been so successful moving to a cloud-based microservices architecture that the company has open sourced many of the tools and components used to build it. In a recent GOTO Conference presentation, Cockcroft explained what led up to Netflix open sourcing much of its code:

"During 2011, there were a bunch of outages where Amazon went down, and Netflix didn't; everyone else went down, Netflix didn't. So why was that? Well it's because we actually architected to be highly available and people said okay well we like that. So in 2012, we [people] said okay we do like these features; it's scalable, it's highly available, we've got a very fast development pipeline, and you stay up when Amazon goes down, and it's low cost, and you keep going up at conferences and battling people, so that looks good. But they couldn't figure out how to do it themselves because the gap from what Netflix was talking about to what everyone else was doing was just too big. So in 2012, we started seriously open sourcing a lot of code."

The Netflix Open Source Software Center (Netflix OSS) provides tools and technologies that companies can use for building a microservices architecture that runs on AWS.

Conclusion
"When we said we were going to move all of Netflix to cloud everyone said we were completely crazy," explained Cockcroft at a recent GOTO conference. "They didn't believe we were actually doing that, they thought we were just making stuff up."

Today, there are many companies that have moved to the cloud adopting a modern microservices architecture including Amazon, Google, IBM, LinkedIn, Nike, Nordstrom, Orbitz, PayPal, Spotify, Target, Twitter, and the list goes on and on.

Netflix was one of the first companies to move to the cloud and implement microservices, helping to pave the way for other companies to do the same. Netflix has become a technology leader, especially when it comes to cloud computing and microservices. This is why just about every article these days that mentions microservices, also mentions Netflix.

Read the original blog entry...

More Stories By SmartBear Blog

As the leader in software quality tools for the connected world, SmartBear supports more than two million software professionals and over 25,000 organizations in 90 countries that use its products to build and deliver the world’s greatest applications. With today’s applications deploying on mobile, Web, desktop, Internet of Things (IoT) or even embedded computing platforms, the connected nature of these applications through public and private APIs presents a unique set of challenges for developers, testers and operations teams. SmartBear's software quality tools assist with code review, functional and load testing, API readiness as well as performance monitoring of these modern applications.

@MicroservicesExpo Stories
Some journey to cloud on a mission, others, a deadline. Change management is useful when migrating to public, private or hybrid cloud environments in either case. For most, stakeholder engagement peaks during the planning and post migration phases of a project. Legacy engagements are fairly direct: projects follow a linear progression of activities (the “waterfall” approach) – change managers and application coders work from the same functional and technical requirements. Enablement and develo...
Admiral Calcote - also known as Lee Calcote (@lcalcote) or the Ginger Geek to his friends - gave a presentation entitled Characterizing and Contrasting Container Orchestrators at the 2016 All Day DevOps conference. Okay, he isn't really an admiral - nor does anyone call him that - but he used the title admiral to describe what container orchestrators do, relating it to an admiral directing a fleet of container ships. You could also say that they are like the conductor of an orchestra, directing...
The past few years have brought a sea change in the way applications are architected, developed, and consumed—increasing both the complexity of testing and the business impact of software failures. How can software testing professionals keep pace with modern application delivery, given the trends that impact both architectures (cloud, microservices, and APIs) and processes (DevOps, agile, and continuous delivery)? This is where continuous testing comes in. D
Modern software design has fundamentally changed how we manage applications, causing many to turn to containers as the new virtual machine for resource management. As container adoption grows beyond stateless applications to stateful workloads, the need for persistent storage is foundational - something customers routinely cite as a top pain point. In his session at @DevOpsSummit at 21st Cloud Expo, Bill Borsari, Head of Systems Engineering at Datera, explored how organizations can reap the bene...
The dynamic nature of the cloud means that change is a constant when it comes to modern cloud-based infrastructure. Delivering modern applications to end users, therefore, is a constantly shifting challenge. Delivery automation helps IT Ops teams ensure that apps are providing an optimal end user experience over hybrid-cloud and multi-cloud environments, no matter what the current state of the infrastructure is. To employ a delivery automation strategy that reflects your business rules, making r...
Gaining visibility in today’s sprawling cloud infrastructure is complex and laborious, involving drilling down into tools offered by various cloud services providers. Enterprise IT organizations need smarter and effective tools at their disposal in order to address this pertinent problem. Gaining a 360 - degree view of the cloud costs requires collection and analysis of the cost data across all cloud infrastructures used inside an enterprise.
SYS-CON Events announced today that Synametrics Technologies will exhibit at SYS-CON's 22nd International Cloud Expo®, which will take place on June 5-7, 2018, at the Javits Center in New York, NY. Synametrics Technologies is a privately held company based in Plainsboro, New Jersey that has been providing solutions for the developer community since 1997. Based on the success of its initial product offerings such as WinSQL, Xeams, SynaMan and Syncrify, Synametrics continues to create and hone in...
Our work, both with clients and with tools, has lead us to wonder how it is that organizations are handling compliance issues in the cloud. The big cloud vendors offer compliance for their infrastructure, but the shared responsibility model requires that you take certain steps to meet compliance requirements. Which lead us to start poking around a little more. We wanted to get a picture of what was available, and how it was being used. There is a lot of fluidity in this space, as in all things c...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex ...
You know you need the cloud, but you’re hesitant to simply dump everything at Amazon since you know that not all workloads are suitable for cloud. You know that you want the kind of ease of use and scalability that you get with public cloud, but your applications are architected in a way that makes the public cloud a non-starter. You’re looking at private cloud solutions based on hyperconverged infrastructure, but you’re concerned with the limits inherent in those technologies.
Gone are the days when application development was the daunting task of the highly skilled developers backed with strong IT skills, low code application development has democratized app development and empowered a new generation of citizen developers. There was a time when app development was in the domain of people with complex coding and technical skills. We called these people by various names like programmers, coders, techies, and they usually worked in a world oblivious of the everyday pri...
The notion of improving operational efficiency is conspicuously absent from the healthcare debate - neither Obamacare nor the newly proposed GOP plan discusses the impact that a step-function improvement in efficiency could have on access to healthcare (through more capacity), quality of healthcare services (through reduced wait times for patients) or cost (through better utilization of scarce, expensive assets).
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The “Digital Era” is forcing us to engage with new methods to build, operate and maintain applications. This transformation also implies an evolution to more and more intelligent applications to better engage with the customers, while creating significant market differentiators. In both cases, the cloud has become a key enabler to embrace this digital revolution. So, moving to the cloud is no longer the question; the new questions are HOW and WHEN. To make this equation even more complex, most ...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task...
For DevOps teams, the concepts behind service-oriented architecture (SOA) are nothing new. A style of software design initially made popular in the 1990s, SOA was an alternative to a monolithic application; essentially a collection of coarse-grained components that communicated with each other. Communication would involve either simple data passing or two or more services coordinating some activity. SOA served as a valid approach to solving many architectural problems faced by businesses, as app...
Many IT organizations have come to learn that leveraging cloud infrastructure is not just unavoidable, it’s one of the most effective paths for IT organizations to become more responsive to business needs. Yet with the cloud comes new challenges, including minimizing downtime, decreasing the cost of operations, and preventing employee burnout to name a few. As companies migrate their processes and procedures to their new reality of a cloud-based infrastructure, an incident management solution...
Cloud Governance means many things to many people. Heck, just the word cloud means different things depending on who you are talking to. While definitions can vary, controlling access to cloud resources is invariably a central piece of any governance program. Enterprise cloud computing has transformed IT. Cloud computing decreases time-to-market, improves agility by allowing businesses to adapt quickly to changing market demands, and, ultimately, drives down costs.
Recent survey done across top 500 fortune companies shows almost 70% of the CIO have either heard about IAC from their infrastructure head or they are on their way to implement IAC. Yet if you look under the hood while some level of automation has been done, most of the infrastructure is still managed in much tradition/legacy way. So, what is Infrastructure as Code? how do you determine if your IT infrastructure is truly automated?
Every few years, a disruptive force comes along that prompts us to reframe our understanding of what something means, or how it works. For years, the notion of what a computer is and how you make one went pretty much unchallenged. Then virtualization came along, followed by cloud computing, and most recently containers. Suddenly the old rules no longer seemed to apply, or at least they didn’t always apply. These disruptors made us reconsider our IT worldview.