Story image

How AWS Lambda enables sharing common code between functions

03 Dec 2018

AWS announced Lambda Runtime API and Lambda Layers, two new AWS Lambda features that enable developers to build custom runtimes, and share and manage common code between functions. 

Lambda supposedly makes it easy for developers to run code for virtually any type of application or back-end service.

The Runtime API for AWS Lambda defines a standardised HTTP-based specification which codifies how Lambda and a function’s runtime communicate. It enables users to build custom runtimes that integrate with Lambda to execute functions in response to events. 

By leveraging the Runtime API, businesses can use binaries or shell scripts, and their choice of programming languages and language versions. 

During an invoke, Lambda will bootstrap the user’s runtime code and communicate with it over Runtime API to execute the function code. With this release, AWS is also publishing a reference implementation of the C++ and Rust runtimes. Users can read more about the Runtime API in the Lambda documentation.

Lambda Layers are a new type of artifact that can contain arbitrary code and data and may be referenced by zero, one, or more functions at the same time. 

Lambda functions in a serverless application typically share common dependencies such as SDKs, frameworks, and now runtimes. With layers, users can centrally manage common components across multiple functions enabling better code reuse. 

To use layers, businesses simply put their common code in a zip file and upload it to Lambda as a layer. They can then configure their functions to reference it.

When a function is invoked, the layer contents become available to their function code. AWS is also providing a layer which includes the popular NumPy and SciPy scientific libraries for Python. These libraries were prebuilt and optimised for use in Lambda’s execution environment. 

By using this layer with Python functions, users can quickly get started with building complex data processing and machine learning applications.

Runtime API and Layers can be used independently. Users can also use them together to publish custom runtimes which can be then shared as layers.

They can also use the AWS Serverless Application Model (SAM) and SAM CLI to test, deploy and manage serverless applications that leverage Runtime API and Layers. 

With this release, several of AWS’ technology partners are also launching their offerings on top of Runtime API and Layers. 

Customers can author functions in new runtimes and layers, including those which support additional capabilities including application management, monitoring, and security.

Microsoft urges organisations to tackle data blindspots
Despite significant focus placed on CX transformation, over a third of Australian organisations claimed that more than one in five of their projects failed.
Raising the stakes: McAfee’s predictions for cybersecurity
Security teams and solutions will have to contend with synergistic threats, increasingly backed by artificial intelligence to avoid detection.
Renesas develops 28nm MCU with virtualisation-assisted functions
The MCU features four 600 megahertz CPUs with a lock-step mechanism and a large 16 MB flash memory capacity.
DOCOMO ranked world's top mobile operator in 5G SEP applications
NTT DOCOMO has been ranked the world's leading mobile operator in terms of applications for candidate standard-essential patents.
Exclusive: Ping Identity on security risk mitigation
“Effective security controls are measured and defined by the direct mitigation of inherent and residual risk.”
CylancePROTECT now available on AWS Marketplace
Customers now have access to CylancePROTECT for AI-driven protection across all Windows, Mac, and Linux (including Amazon Linux) instances.
Gartner’s top 10 data and analytics trends for 2019
Data is the fuel for the modern world, and analytics the engine. Gartner has compiled the top 10 trends to watch this year.
How CIOs can work with colleagues to drive new competitive advantages
"If recent history has taught us anything, it’s that the role of the CIO is always changing, and that it won’t stop changing anytime soon."