There are many reasons to install serverless. And they are discussed on Serverless Chats podcast hosted by Jeremy Daly and Rebecca Marshburn. We tuned into their podcast with Chris Munns. We are big fans of Chris and all he has done at AWS to help the serverless community succeed. This episode is great.
Here is the blurb on Chris Munns from the podcast:
Chris Munns is a Tech Lead/Advisor for Startup Solution Architects at Amazon Web Services based in New York City. Chris spent the last 4.5 years working with AWS’s developer customers to understand how serverless technologies can drastically change the way they think about building and running applications. At potentially massive scale with minimal administration overhead. Before this, Chris was a global Business Development Manager for DevOps at AWS. He spent a few years as a Solutions Architect at AWS. And has held senior operations engineering posts at Etsy, Meetup, and other NYC based startups. Chris has a Bachelor of Science in Applied Networking and System Administration from the Rochester Institute of Technology.Serverless Chats
- Twitter: @chrismunns
- Email: email@example.com
- AWS Compute Blog: https://aws.amazon.com/blogs/compute/
Install serverless – code is a liability
We use the term ‘code is a liability‘. It asks tech professionals to transition to ‘less building’. And deliver more on ‘business value’. This is hard for engineers to do as they naturally like to build!
It is essential for your tech stack to evolve into a commodity. You need to switch your perspective. And see that your system and the outcomes it delivers is the asset. The underlying code is the liability. Engineers should not be continually buried in code. Teams should design and deliver differentiating capabilities. And drive improvements on ‘time to value‘.
Engineering teams need to implement more managed services. And SaaS and direct service integrations. By doing this, they can free up their time and intellectual resources. And have less custom code liabilities to manage. And lower operational burden to support.
Code is a liability and here’s why
Jeremy and Rachel cover the evolution of Serverless, developer advocacy and startup advice with Chris. Chris’ views align to our ‘code is a liability’ maxim:
- Amazon are going to build services to enable developers and operations people. They do not have to build and run stuff themselves
- Remove burden, operational toil and low hanging work
- Continued evolution. By saying: how can we simplify this and make this better for certain workloads in certain places?
- The collective benefit of services being put together. And the direct outcome of agility and faster time to reduced operational burden
- Finding ways to continue to reduce operational burden. With more managed services and even less code to maintain and write. You’re spending more time on the product side. And delighting your customers and leadership. It’s a no brainer.
Evolution to Functionless
Serverless, managed services, richer configuration options and more direct service to service integrations continue to evolve. We believe custom lambda code liabilities start to reduce over time. This leads to a ‘Functionless’ model.
The recent announcement that AWS Step Functions Supports 200 AWS Services is a game changer! It adds massive direct power into the Step Functions managed service. This has huge potential to help engineering teams evolve their solutions. And rapidly integrate new capabilities and remove large portions of custom code.
The entire episode is great and well worth 60 minutes of your time!