What is AWS Lambda?May 22, 2019 AWS
The AWS Lambda is a responsive cloud service that inspects actions within the application and responds by implementing user-defined codes, known as functions. The AWS Lambda supports the code written in Java, Python and Node.js, and the service can initiate processes in languages supported by Amazon Linux (which can initiate processes in languages compatible with Amazon Linux, including Bash, Go and Ruby.) , some tips recommended when using the AWS Lambda.
- Never declare any function variable outside the scope of the controller • Make sure, if you have a set of + rx permissions in your files in the zip code sent to ensure that Lambda can run the code in your name.
- Delete old Lambda functions when they are no longer needed.
AWS Lambda Functions :
The code that runs on the Lambda AWS is called the “Lambda function”. After creating your Lambda function, it will always be ready to run as soon as it is triggered, similar to a formula in a spreadsheet. Each function includes its code, as well as some associated configuration information, including the name of the function and the resource requirements. The Lambda functions are “stateless”, with no affinity to the underlying infrastructure, so that the Lambda can quickly start how many copies of the function are needed to stagger the rate of events received.
After loading your code into the AWS Lambda, you can associate its function with specific AWS resources (for example, an Amazon S3 cube, an Amazon DynamoDB table, an Amazon Kinesis flow, or an Amazon SNS notification). Then, when the resource is changed, the Lambda will execute its function and administer the computing resources, as necessary, to accompany the received requests.
AWS Lambda Limitations
In general, the serverless architecture is not efficient for running long-term applications; In these cases, containers or EC2 instances are more appropriate. Another interesting limit is the size of the Lambda function implementation package, which is set to 50 MB (compressed), and the non-persistent draft area available for the use function – 500 MB. Another important issue to consider is the AWS Lambda Cold begin. It takes some time for the Lambda function to manipulate a first request, because the Lambda needs to start a new instance of the function. The cold exit can be a real problem for your function, if at any time you expect a quick response and there are no active instances of its function. The latter can occur in low traffic scenarios, when AWS closes instances of its function when there are no requests for a long time.
An alternative solution is to send a request periodically to avoid initial startup and ensure that there is always an active instance, ready to respond to requests. Other functional limitations include:
- Lambda functions are short-lived, so they must persist somewhere. The available options include the use of DynamoDB or RDS tables, which require fixed payments per month.
- Lambda functions record their records in CloudWatch, which is currently the only tool to solve problems and monitor their functions.
Lambda applications use cases
Lambda’s serverless application model is generic and can be applied to virtually any type of application, from the simple web application of a start-up company to the stock trading analysis platform of a Fortune 100 company. Here are some examples where the Lambda can be used:
Web apps and websites
By eliminating servers, you can design Web applications that cost nothing when there is no traffic. The server can scale dynamically at peak times to handle excessive traffic loads.
Mobile serverless backends make it easy for developers to easily create secure, available and perfectly sized back-ends, without having to acquire specialized knowledge in the development of robust applications.
Media and log processing
A serverless approach offers natural parallelism, making it easier to process workloads. You do not need a multi-engineered complex system or you need to scale whole computing fleets to handle heavy workloads.
Serverless functionality can be easily exploited and customized as needed, as and when necessary. It becomes very simple and easy to scale applications when the nature and scope of your business change.
You can incorporate any native code and libraries to simplify the creation of algorithms specific to cloud-based devices.