When DevOps Meets Serverless

Editor's Notes

• #2: DevOps engineer – focusing on serverless, working on fintech project at moment. Talking about serverless and how DevOps is evolving to meet its challenges.
• #3: So what is serverless? Well, a vast amount of security, scalability and managing failover is someone else's problem – Amazon and Microsoft will take care of this with serverless, rather than giving you a virtual server to manage.
• #4: Serverless is like PaaS, only more so – you just deploy app code as stateless functions. The difference is auto scaling and high availability – the cloud provider runs as many servers as you need.
• #5: FaaS = run single stateless function, as many copies as needed - no problem with Wall of Traffic - very good for spiky workloads
• #6: The other part of serverless is BaaS = Azure Blobs, AWS S3, Cosmos DB, DynamoDB, … all run by the cloud provider so you don't have to.
• #7: If you use any of those BaaS services with servers or containers, you are partly serverless! It's very common to do this, to avoid the hassle of running your own object store, database, or whatever – and that's the same logic that drives serverless.
• #8: Most servers are mostly idle, like this guy. A key part of serverless is that you don't pay for idle time. Just pay as you go, for the compute and storage you use. Ref: https://www.slideshare.net/NCore1/unite-2017-going-serverless-gertjan-vanthienen slide 2 - servers are 30% idle, and on AWS it's over 90%.
• #9: So serverless has many benefits for scaling, security and so on. The question is: does this mean Less Ops or No Ops?
• #10: I believe that DevOps is not disappearing, but evolving in response to some of the new challenges as you move into the serverless world, to make sure your app *keeps working* in production.
• #11: Provisioning cloud resources such as storage containers, or access controls, requires tools such as Terraform, and typically a deployment tool like Serverless Framework. Configuration parameters apply in all these cases, and a DevOps mindset helps in keeping them DRY.
• #12: For many cloud resources, "infrastructure as code" is a key part of DevOps - here we're creating a container in Azure Blob Storage using Terraform.Just like app code, this code goes into Git, gets code reviewed, and has automated tests done in CI/CD.
• #13: You still need to detect your app isn't working, or is too slow - so monitoring and logging remain crucial. The complexity of serverless architectures also drives the need for observability, which lets you drill down into really hard bugs in production, by capturing rich data that's easily analysed.
• #14: Each serverless function is an independent unit, acting as a nanoservice, not just a microservice. That's great for scaling, but you now have more to monitor and configure than before.
• #15: DevOps for Serverless means knowing the best way to do operational stuff, based on the details like how Azure storage accounts affect IOPS, or how AWS handles "cold start" of a Lambda function - this stuff really matters to how well your app works in production.
• #16: Secret management means making sure all your passwords and API tokens are properly encrypted. Cloud providers have some great value services here, like AWS Parameter Store, but they still need to be configured.
• #17: Good news - you have no servers to harden! The bad news is you can't deploy security related agents to those non-existent servers. Serverless needs some new tools and approaches here – both vendors and cloud providers are focusing on this.
• #18: Development environments can be very low cost with serverless – everyone can get their own environment. Canary deployments for a percentage of traffic were tricky but are now supported by some cloud providers.
• #19: Serverless Functions can't do everything yet – long-running processes or guaranteed low latency are reasons why you may have servers or containers lurking in the background. Not a long-term reason for DevOps on every project, but still a factor.
• #20: Serverless has real benefits for developers and the business – running those invisible servers is "someone else's problem", and you get a lot of security, scalability and high availability, "Don't Pay for Idle" is a key point, giving huge cost savings. DevOps is already evolving to meet the challenges of serverless.
• #21: This has been a very quick tour of how Serverless is changing DevOps. Thank you!