Think of it as "document root " in apache/nginx configuration where we define the path of our code and where exactly our code is residing.
Api-Gateway
Think of it as configuration files in “sites-enabled” in nginx with all the required flags like.
server_name
location
alias
headers information etc
So the document root is siting there idle until/unless we don’t have any request on our nginx configuration asking about our application.
Same goes with Lambda and Api-gateway as well, you don’t get your lambda code running until it’s triggered by Api-gateway (or from some other services)
AWS, Short for Amazon Web Services is a cloud computing platform developed by Amazon. Lambda is a server less cloud computing platform developed as part of the AWS. The purpose of Lambda is to build smaller, on-demand applications that are responsive to events and new information. With AWS Lambda, the servers are managed by Amazon which allows developers to focus on writing code. Lambda supports programming languages like Python, Node.js, Java and C#.
API-Gateway is service that allows a developer to connect non-AWS applications to AWS back-end resources, such as servers or code. The purpose of API is to facilitate communication between two or more software programs. An AWS user creates, manages and maintains APIs within Amazon API Gateway. The service manages traffic, authorizes end users and monitors performance.