An insightful comment. k8s and Lambda aim to solve the problem of service management & deployment. k8s focuses on abstracting the server underneath and automa

An insightful comment. k8s and Lambda aim to solve the problem of service management & deployment. k8s focuses on abstracting the server underneath and automating its operations, aka orchestration, "in-the-weeds & full control". Lambda instead focuses on outsourcing the server and its operations to AWS, aka serverless, "don't even think about it". Infrastructure engineers value the wide & deep featureset of k8s, and will accordingly invest significant manpower into its maintenance. Business developers value the simplicity of lambda and appreciate its low overhead and low price. The tension between these two solution & their audiences is resolved by the value-chains emanating from the top of their organizations. In a startup phase, leaders will likely value Lambda over k8s because managing services is not a core competency, i.e., they don't care enough. "Just get the application on prod and make sure it doesn't go down! How hard can that be?" As the organization develops over time, situations will arise that cannot be solved easily by Lambda or are too expensive to work on Lambda, which will necessitate expensive solutions like k8s. The leaders don't want to care about uptime, for example, so they'll hire people who do, people who have a different sense of value and cost. I think it's telling that the presenter of Lambda at AWS is not the CTO, but the CPO himself: https://aws.amazon.com/solutions/case-studies/netflix-and-aws-lambda/ https://aws.amazon.com/solutions/case-studies/netflix-and-aw... Four years later, an engineer gave a presentation about how Netflix built their own in-house FaaS, seemingly outgrowing Lambda: https://www.slideshare.net/yunongx/going-faaster-functions-as-a-service-at-netflix https://www.slideshare.net/yunongx/going-faaster-functions-a...