Cloud Traffic
I do wonder what the equivalent review of AWS Lambda would look like from an equivalent writer but one versed in GCP and K8S, encountering Lambda and IAM for the first time.<p>I think one can easily make concerning arguments about all the things Lambda abstracts away and how concerning that is.<p>HAVING SAID THAT, the substantial fundamental difference between something like Lambda and something like K8S is the value proposition. Lambda works backwards from your business logic. How to go from 0 to &quot;working production code&quot; with the minimal amount of steps, yet will still scale essentially infinitely (so long as you are willing to tolerate the latency costs)<p>K8S seems to me like it instead works backwards from your infrastructure. How to go from one set of working infrastructure to another set of working infrastructure, but one optimized for solving problems that your organization doesn&#x27;t have yet until you&#x27;re at the point where you&#x27;re looking to migrate your whole cloud strategy to another provider because Azure gave you a 2% higher discount than AWS did.<p>Meanwhile, by the time you&#x27;ve built your first working K8S-based architecture, your competitor with Lambda is already in production serving customers.<p>I know, I know, it&#x27;s not Apples and oranges. But K8S and Lambda are of the same &quot;generation&quot;, both launching in 2014. Lambda was AWS&#x27;s big bet of &quot;Here is the amazing value you can get if you go all-in on AWS-native development&quot;, K8S was GCP&#x27;s equivalent &quot;Here&#x27;s how you can design your cloud infra to be portable if you explicitly DON&#x27;T want to go all-in one cloud provider.&quot;<p>So while they offer almost diametrically opposite solutions (philosophically), they are pursuing the same developers to convince them of the mind share.<p>Me, I&#x27;ll take the one that actually cares about getting me to production with working business logic code.