Core Concepts
The author emphasizes the importance of efficient internal tooling to support developer productivity at Netflix, focusing on a federated model and the build vs. buy debate.
Abstract
Efficient internal tooling at Netflix is crucial for developer productivity. The company follows a federated model where different pillars provide tools and infrastructure to support developers. The build vs. buy debate is highlighted, emphasizing the need to evaluate whether owning and maintaining tools is worth it.
Netflix's approach involves enabling developers to build, test, own, and operate their software efficiently. They emphasize adapting tools to fit specific needs and languages while considering factors like scalability, latency, and industry advancements. The use of community-supported models and close collaboration with vendors are key strategies employed by Netflix.
To measure developer productivity improvements, Netflix focuses on metrics like Satisfaction, Performance, Activity, Communication, Efficiency (SPACE), as well as customer interviews and surveys. Operational metrics like deployment frequency and change failure rate are also utilized through DORA.
Stats
"If we don't hit the 85% use case that our customer needs, they can choose to use something else."
"Companies that started a while ago had to build their tools from scratch as there was nothing on the market to meet their needs at the time."
"There is a lot of demand for Python when it comes to machine learning, personalization, etc."
Quotes
"We have more of a federated model where we support our developers to leverage our platforms, tools, and infrastructure."
"It is often more sustainable to buy tooling if there is something on the market that can fulfill the need."
"How quickly can somebody go from idea to pushing that idea out the door?"