#Serverless all things! General Manager, AWS Lambda Experience @AWScloud. Dad/Gamer/Foodie with knowledge of comic books and mythology. Now with opinions!
Jan 26, 2020 • 9 tweets • 2 min read
Sunday musings as I write an exec doc - It’s critical for those us building “way of life” tech to understand the human factors of our offering. For example, whatever you think of Kubernetes as a technology, it has a very powerful force working in its favor : Hope.
Hope to those with decades of Software experience of continuing to use software skills in a services world, and to those providing those services a way to attract those populations.
May 22, 2019 • 5 tweets • 1 min read
Someone asked me today if a function was just a container packaged as a ZIP. Wellll .. not quite. Packaging format isn’t a durable difference, nor it should be. 1/5
First, some terms cos containers is as overloaded as serveless - images define what runs, containers is a running of the image. Crazy how often folks conflate the two. Let’s also leave aside the “aaS” part of FaaS vs orchestration in containers. 2/5
Dec 18, 2018 • 8 tweets • 3 min read
2019 Wish : The #serverless community practices what it preaches, and focuses the conferences/talks/articles on the value gained, rather than the technology and concepts. In fact, we probably need to have some basic rules for serverless content. For example -
1) Must identify yourself as a practitioner (someone leveraging #serverless technologies to build something of end customer value) or a provider (someone who is providing technology that elables a practitioner to go serverless).
Jul 24, 2018 • 5 tweets • 1 min read
Interesting to see FaaS and Serverless compute start to diverge.
Strongly believe the latter needs to eliminate all routing, placement, scaling, management, packing, and patching responsibilities from your domain while meeting your availability, latency, and scale needs. Doing any of that yourself is work you shouldn’t do.
Mar 16, 2018 • 5 tweets • 2 min read
When I tell people I am the founding PM on Lambda, the question I often get is how the idea for #AWS Lambda/#Serverless came about in the first place. The truth is, its way too hard to point to one person/event as the defining moment.
It took 100s of customer conversations notes from multiple AWS folks where they told us 1/all the things they wanted to minimize/ not do at all while building applications; 2/architectural patterns they were repeating and wanted a way to build into their development flow.
