InfoQ Homepage Netflix Content on InfoQ
-
Netflix Open Sources Their Domain Graph Service Framework: GraphQL for Spring Boot
Within a few months of implementing their Domain Graph Service Framework (DGS), Netflix has open-sourced DGS to the Java community. This framework improves the usage of GraphQL for standalone and federated GraphQL services. InfoQ spoke to Paul Bakker, senior software engineer at Netflix and committer for DGS, about open-sourcing the DGS framework.
-
Netflix Implements GraphQL Federation at Scale
Netflix has successfully implemented a federated GraphQL API at scale. In a recent blog post series, engineers from Netflix describe their journey and the lessons learned in the process. With GraphQL federation, the API gateway implementation is distributed to backend teams owning the individual domain services they implement instead of centrally developed as part of the API gateway.
-
Maximizing User Experience with Prioritized Load Shedding at Netflix
Netflix uses its homegrown API gateway, Zuul, to classify incoming requests into priorities. When the system comes under load or is otherwise unstable, Zuul throttles traffic, starting with the lowest priority. It then progressively adjusts to shed load according to the priorities calculated until the system is healthy again.
-
Netflix Presents Telltale, an Application Health Monitoring Tool
The Netflix Engineering team recently blogged about Telltale, a monitoring and alerting tool that utilizes a variety of data sources to learn the typical health of an application. Telltale shows only the relevant data from application. There's also information about important events, such as nearby deployments and regional traffic evacuations.
-
Netflix Open Sources Crisis Management Orchestration Tool
Netflix announced the release of Dispatch, their crisis management orchestration framework. Dispatch integrates with existing tools such as Jira, PagerDuty, and Slack to streamline the crisis management process. Dispatch includes integration endpoints for adding in support for additional tooling.
-
Delta – a Data Synchronization and Enrichment Platform by Netflix
Large systems often utilize numerous data stores. There is sometimes a need to keep some of these data stores in sync, and to enrich data in a store by calling external services. To address these needs, Netflix has created Delta, an eventual consistent, event-driven data synchronization and enrichment platform. In a blog post, the team behind Delta gives an overview of their design.
-
Managing Global CDN Operations at Netflix
At the recent Strange Loop conference, Robert Fernandes, engineering manager at Netflix, who leads the Open Connect Tools team, gave a talk on how they manage operations for Netflix’s in-house OpenConnect content delivery network (CDN).
-
Google Introduces Spinnaker for GCP, Simplifying the Configuration of Continuous Delivery
Spinnaker is an open-source multi-cloud continuous delivery platform co-developed by Google and Netflix. In a recent blog post, Google introduced the Spinnaker for Google Cloud Platform solution, which allows customers to install and run Spinnaker in the Google Cloud Platform (GCP).
-
How Did Things Go Right? Learning More from Incidents at Netflix: Ryan Kitchens at QCon New York
At QCon New York, Ryan Kitchens presented “How Did Things Go Right? Learning More from Incidents”. Key takeaways from the talk included: recovery is better than prevention; an incident occurs when there is a “perfect storm” of events -- there is no root cause; “stop reporting on the nines”, as user happiness is more important; and there is value in learning how things go right.
-
Netflix Play API: Building an Evolutionary Architecture
At QCon SF, Suudhan Rangarajan presented “Netflix Play API: Why We Built an Evolutionary Architecture”. Key takeaways included: services that have a single identity/responsibility are easier to upgrade; spend time identifying core decisions that need to be made when building a service; and designing an “evolutionary architecture” using tools like fitness functions provides many benefits.
-
The Evolution of Full Cycle Developers at Netflix: Greg Burrell at QCon SF
At QCon San Francisco, Greg Burrell talked about the journey towards “full cycle developers” within the Netflix edge engineering team. Following the principle of “operate what you build”, developers within this team chose to take on more operational responsibility for their services, and were facilitated by comprehensive tooling, training and management support.
-
Building Resilience in Netflix Production Data Migrations: Sangeeta Handa at QCon SF
At QCon SF, Sangeeta Handa discussed how Netflix had learned to build resilience into production migrations across a number of use cases. Key lessons learned included: aim for perceived or actual zero downtime, even for data migrations; invest in early feedback loops to build confidence; find ways to decouple customer interactions from your services; and build independent checks and balances.
-
Netflix Keystone Real-Time Stream Processing Platform
Netflix recently published a post in their tech blog discussing the design considerations and insights of Keystone, their Real-time stream processing platform. Keystone has been operational since December 2015 and has grown significantly over the years as Netflix subscribers have grown from 65 to over 130 million in the past 3 years. This article follows on the latest state of Keystone platform...
-
Scaling Push Messaging for Millions of Devices @Netflix - Susheel Aroskar at QCon NY
Susheel Aroskar from Netflix's Engineering team spoke at the recent QCon New York 2018 Conference about Zuul Push, a scalable push notification service that asynchronously pushes data like personalized movie recommendations from cloud to devices.
-
Full Cycle Developers at Netflix: from Mindsets to Self-Service Tooling
The Netflix Tech Blog has shared the story of the “Edge Engineering” team’s journey of experimenting with approaches to building and operating services, which has culminated in “Full Cycle Developers”. This approach is showing promise with Netflix, where developers are responsible for certain operational aspects of service delivery, and are supported through a range of self-service tooling.