AWS Lambda

Short Summary

Amazon Web Services (AWS), founded in 2006 as a subsidiary of Amazon.com, has become the world’s largest cloud provider by offering a broad portfolio of IT infrastructure services across compute, storage, networking, databases, mobile, analytics, application development, and IoT management. With global data centers across 16 geographic regions, millions of customers, aggressive pricing, and a large partner network, AWS is positioned as a default “cloud” choice for organizations aiming to cut IT costs and overcome scalability constraints.

Cloud adoption reshapes not only operations but software development: teams want faster delivery, elastic scaling, and the ability to offload commodity capabilities (such as authentication or messaging) to managed services. Yet even in the cloud, developers still manage infrastructure (provisioning virtual machines, securing networks). Serverless computing—Function as a Service (FaaS)—pushes further by removing infrastructure management, letting developers build systems as small independent services or functions invoked via standard APIs, while the provider provisions resources and bills only for requests served.

AWS Lambda, introduced in 2014, is an event-driven serverless platform where “Lambda functions” execute on demand, integrate tightly with services like S3, DynamoDB, Kinesis, SNS, and API Gateway, and can be orchestrated using AWS Step Functions. Lambda supports Node.js, Python, Java, and C#, can use third-party and native libraries, and can run Linux executables within a sandbox. Use cases include S3-triggered image thumbnail generation and real-time stream processing for IoT and social media. Identity and access control rely on AWS IAM. Recent extensions include Lambda@Edge for low-latency execution at CloudFront edge locations and AWS Greengrass to run Lambda locally on connected devices. Key limitations include cold-start latency, unsuitability for long-running workloads, potential vendor lock-in, limited logging/monitoring, and lack of built-in local testing.

Interesting Facts

• AWS was established in 2006 as a subsidiary of Amazon.com, Inc.
• AWS offers over 90 IT infrastructure services spanning compute, storage, networking, databases, mobile, analytics, application development, and IoT tools.
• AWS operates data centers in 16 separate geographic regions worldwide.
• AWS Lambda was first introduced in 2014.
• AWS Lambda is an event-driven serverless computing platform.
• Lambda pricing is based on 100-millisecond increments rather than hourly billing used by services like EC2.
• AWS Lambda natively supports Node.js, Python, Java, and C#.
• Lambda can run Linux executable files and can start background processes in a sandbox environment.
• Lambda integrates with S3, DynamoDB, Kinesis, SNS, and can be exposed via Amazon API Gateway.
• AWS Step Functions can coordinate multiple Lambda functions and other components using visual workflows.

Notable Quotes

• “This serverless computing approach, also known as Function as a Service (FaaS) provides multiple benefits for developers, allowing them to focus solely on business functionality and not on infrastructure management.”
• “Customers are only paying for actual requests served by their code.”
• “Customers do not need to pay when their code is not running.”
• “A textbook example of a Lambda function is an image thumbnail creation function, which is triggered by new images uploaded to an S3 bucket to create multiple resized versions for a website, a mobile app and so on.”
• “Such applications require no administrative effort to set up scalability or redundancy across multiple datacenters - AWS Lambda takes care of it automatically.”
• “The notion of identity and access management is integral for AWS Lambda.”
• “Lambda@Edge feature allows developers to run their code directly at global AWS edge locations to ensure the lowest latency for responding to end users without the need to route requests to a centralized server.”
• “With all the impressive capabilities of Amazon’s serverless computing platform one has to remember that the concept has its limitations.”
• “Finally, Lambda does not provide any built-in tools for testing functions locally, so running a debugging session in the cloud will inevitably incur additional costs.”
• “Even considering its current shortcomings, Lambda already provides a revolutionary way to develop new applications and APIs in a more time- and cost-efficient manner than ever before.”