Serverless?! (AWS Lambda)

Lately there’s been a lot of fuss about serverless. But what the hell does serverless even mean? Let’s see if I can provide a brief explanation.

The last two years at work, I’ve been gradually moving our on-premise infrastructure up into “the cloud” (AWS and DO mainly). At this point, about 85% of all the company’s infrastructure is now in “the cloud”. Which brings us to AWS Lambda and serverless. How the hell could something be serverless? Well what they really mean is that you don’t have to worry about the server. You write some code and the code will be triggered to run and you don’t have to provision a server, install the dependencies, etc. Sounds cool, right? Yes. And more importantly to the company, it can help save a lot of money.

There’s a few things that I could transition to AWS Lambda. Until recently though, Lambda didn’t support Python 3.x and that meant it wasn’t something that I wanted to deal with. But that has changed now and Lambda supports Python 3.6. So in the next month or so, I’ll be playing around with it and hopefully can migrate some stuff over and save the company some more money. Should be a fun side project.

Till next time…