Serverless
Serverless computing is a cloud-computing execution model in which the cloud provider dynamically manages the allocation of machine resources. Pricing is based on the actual amount of resources consumed by an application, rather than on pre-purchased units of capacity. It is a form of utility computing.
Serverless computing still requires servers, hence it's a misnomer. The name "serverless computing" is used because the server management and capacity planning decisions are completely hidden from the developer or operator. Serverless code can be used in conjunction with code deployed in traditional styles, such as microservices. Alternatively, applications can be written to be purely serverless and use no provisioned servers at all.
Source: https://en.wikipedia.org/wiki/Serverless_computing
Position on the Adoption Curve
Presentations about Serverless
Observability to Better Serverless Apps
Serverless Patterns and Anti-Patterns
Serverless + Containers = Modern Cloud Applications
Serving Millions of Customers Serverless at CapitalOne
Serving Millions of Customers Serverless at CapitalOne
Serverless Workshop
Interviews
Seamlessly Migrating To Serverless with 80-Million Users
Is your talk a story of a migration to a serverless architecture through a devops lens or maybe are you talking about practices and patterns for serverless? What's the angle that you're taking with your talk?
I'm starting with just building a little bit of a foundation for what I feel devops actually is. There's a lot of charts about like the process project creation, packaging, releasing, and monitoring in a serverless world. Then start talking about devops for us.
What I'm hearing is that serverless is a part of it, but the big theme is devops. Is that right?
Yeah. It's basically painting a picture of serverless devops today. We placed a bet on serverless. These are the things that happened along the way and where we wound up.
