AWS Lambda Project with .NET Runtime
Examine the structure of an AWS Lambda project with .NET runtime.
An AWS Lambda project with .NET runtime
AWS Lambda can be written as .NET executables that use .NET runtime. When it’s done this way, the AWS runtime doesn't run the .NET code. Instead, it spawns a .NET runtime process, which runs as a standard .NET executable within AWS.
The following playground contains an example of an AWS Lambda project with .NET runtime. This project represents a basic function that accepts a textual input, converts all the letters in the input to uppercase, and returns the results to the sender.
{
"Information": [
"This file provides default values for the deployment wizard inside Visual Studio and the AWS Lambda commands added to the .NET Core CLI.",
"To learn more about the Lambda commands with the .NET Core CLI execute the following command at the command line in the project root directory.",
"dotnet lambda help",
"All the command line options for the Lambda command can be specified in this file."
],
"profile": "",
"region": "",
"configuration": "Release",
"function-architecture": "x86_64",
"function-runtime": "dotnet6",
"function-memory-size": 256,
"function-timeout": 30,
"function-handler": "LambdaApp"
}The following diagram demonstrates how each event is handled by an AWS Lambda application with .NET runtime.
In this setup, the AWS Lambda application runs under its own runtime. It attaches its event handler to a message queue. Any event that comes in is handled by AWS event bindings that have been configured to listen to a specific event type. An event may be an HTTP request, a database event, or a message from a message broker, for example.
Once the event is received by the AWS bindings, its data is placed on an internal message queue. The AWS Lambda application listens to this queue and reacts to the events. It doesn’t need to know anything about where the data came from. As long as the shape of the data matches the expected format of the input parameter, the logic in the function handler is triggered.