Introduction to deploying AWS resources using the serverless framework.
Here we will build some foundations and expand our knowledge about the Serverless Framework and show that it is an effective tool when it comes to deploying serverless applications.
Previously, in Part I of this series, we discussed and compared tools that can be used for deployment of serverless applications and supporting infrastructure.
Please do bear in mind that this series is AWS and Node.JS biased, but similar concepts still apply across any cloud and any programming language.
Deep-ish dive into the serverless framework
Now, that I told you that the serverless framework could deploy infrastructure, you may wonder why Terraform can be a useful tool to deploy supporting infrastructure. All that is coming in Part III, but let’s have a look at an example of a simple serverless app. …
The general belief is that Terraform is the de facto way of deploying infrastructure across multiple platforms. On the other hand the Serverless Framework is more specific and aims to aid deployments of Serverless applications across multiple platforms.
There are clear benefits of being generic, and there are benefits of being specific. However, I am going to attempt to convince you why I believe that deployment of Function-as-a-Service (FaaS) and infrastructure resources on AWS ought to be deployed using the Serverless framework in conjunction with Terraform and they are not mutually exclusive.
First, we need to appreciate the fact that a multitude of tools exists when thinking about deploying infrastructure resources. Each of these tools seems to offer a slightly different approach to solve the same problem. Unsurprisingly, it seems to boil down to personal preference or market demands when it comes to picking the right tool. Let me clarify; the tool is right when it fits your use case, the current skills and the audience. …