As the technology world continues to evolve, one area where there is a continual paradigm shift is in serverless computing. It used to be a large piece of “metal” would serve multiple functions (back in the mainframe days), and as servers evolved they became smaller and companies would be one for each “application” or “function”. As time went on we started to virtualize these servers and the big thing in the last 3 years has been containers. Containers allow companies to separate the application from the operating system, allowing faster development; hence the ability to roll out applications faster and keep or build a competitive advantage.
In the last 18 months or so, serverless computing has started to really take shape. Companies big and small are embracing this new way of thinking as it allows them the ability to not have to think – it just works. Based on the type of application built and some of the parameters needed to run, the big public cloud providers will just take care of the rest. As capacity is needed, it will automatically spin up, when it is not being used it will spin down. This allows companies to really keep an eye on spending in the public cloud as well since resources are dynamically allocated and billed for.
One area we have been spending a lot of time at Pliant playing around with is the Lambda functions from AWS. We are continually amazed by how fast applications can be built, packaged, deployed, and of course automated. One item that is near and dear to our heart is how do you automate these newly created functions and applications? Luckily providers such as AWS allow the ability to create REST APIs for each of these. So the question for you is, how are you automating your serverless “infrastructure”?