When you are building microservices-based serverless applications, one of the important things will be communication between the services. When we talk about serverless in AWS, the first thing that comes to mind is the AWS Lambda service provided by AWS. In this post we will focus on how do you
Amazon API Gateway [https://awsmag.com/introduction-to-api-gateway/] is a fully managed service that helps developers to create and deploy scalable APIs on AWS. These APIs act as an entry point for the applications to connect and get access to data, perform business logic or access any other AWS service. In
Serverless Architectures using AWS Lambda and other services provided by AWS like Amazon API Gateway are becoming popular when you don't want to have an overhead of maintaining the servers.
In one of the previous blog posts, we have talked about creating an AWS Lambda function using Node.js [https://awsmag.com/getting-started-with-aws-lambda-and-node-js/] and deploying it using the console. We used a template function provided by AWS and use the console to configure it. We have also talked about What
AWS SAM (Serverless Application Model) [https://awsmag.com/what-is-aws-sam-serverless-application-model/] is an open-source framework to develop and deploy serverless applications on AWS. In this blog post, we will try to understand the AWS SAM Template, its various parts and how to write one for developing and deploying serverless applications on AWS.
In the previous post of this series, we have talked about AWS Lambda [https://awsmag.com/an-introduction-to-aws-lambda/], AWS SAM [https://awsmag.com/what-is-aws-sam-serverless-application-model/]and what is serverless computing [https://awsmag.com/what-is-serverless-computing/] in general. In this post, we will write a small function that can be deployed to AWS Lambda