Going Serverless: Lambda@Edge and Amazon Aurora Serverless

Lambda@Edge

Lambda@Edge is a new Lambda-based processing model that allows you to run functions in response to various Amazon CloudFront events—in AWS locations that are closer to the end user. It can modify CloudFront requests and responses and has many practical use cases, including:
  • Creating new HTTP responses that redirect unauthenticated users to login pages.
  • Inspecting cookies in order to rewrite URLs to different versions of websites for testing purposes.
  • Inspecting headers and authorized tokens for access control before deciding whether to forward a request.
  • Adding, deleting, and modifying headers.
  • Rewriting URL paths to redirect users to different locations, depending on need.
To use Lambda@Edge, simply write a piece of code (AWS offers several examplesfor Lambda@Edge functions) and set up the trigger to be a specific CloudFront event. After the trigger is set, your function will be replicated to multiple AWS edge locations. These locations are part of the AWS global infrastructure, which is used to provide low latency connectivity by making static content accessible from the geographical location closest to the request.

                                                 Global distribution of a Lambda@Edge function

When working with Lambda@Edge, there are multiple limitations to consider, such as the default limits for both AWS Lambda and CloudFront, as well as additional limits specific to Lambda@Edge. These additional limits include soft limits regarding the number of triggers, concurrent executions, or requests per second; and hard limits that differ by event type.  

AWS Serverless: Moving Forward

For a long time, serverless computing revolved primarily around Lambda functions. This changed at AWS re:Invent 2017, when Amazon announced Aurora Serverless, a new AWS service that applies the concept of event-driven cloud computing to databases.

Amazon Aurora Serverless

Amazon Aurora Serverless is a service based on Amazon Aurora, a MySQL and PostgreSQL compatible database built for the cloud. It allows you to start up, shut down, and scale up or down your database compute capacity based on your application’s needs—without provisioning or managing servers yourself. This is achieved by separating compute processing from storage.
When using Aurora Serverless, simply create a database endpoint and start issuing queries. Unlike with standard databases, your endpoint is only a proxy that routes queries to a fleet of “warm” scalable database servers. This allows you to scale up quickly when needed, as new resources are online within seconds. It also allows you to scale down completely when there are no workloads to be processed. When this happens, you only pay for storage capacity. Databases require large amounts of processing power and produce significant costs, so this makes Aurora Serverless an incredibly valuable product.
Aurora Serverless is also a great choice for use cases that are unpredictable or intermittent, such as reporting workloads, sales events like Black Friday, online gaming applications and software, and development and testing purposes. You can sign up for a free preview here.

Summary

Although the concept of serverless is still somewhat new, its benefits are substantial. AWS Lambda introduced possibilities that were previously unthinkable, allowing us to focus completely on the product and speed up delivery time, rather than provisioning and maintaining infrastructure. In doing so, it completely changed the way we look at the cloud.
The recent announcement of Amazon Aurora Serverless showed us that AWS Lambda was just the beginning of the serverless revolution. With Aurora Serverless, the benefits of serverless are applied to databases, marking a huge step forward and inspiring us to think about what is yet to come.
I am extremely passionate about Cloud Computing and the impact it has had on the software industry. My mission is to enable SaaS product companies to scale, and continuously innovate as market leaders by leveraging the modern platform mindset and its untapped technology potential. Enabling technology to deliver on business scale and growth. Data driven decision making and connected delivery to bring together business, product and technology.

Popular posts from this blog

"Amazon.Lambda.RuntimeSupport" .NET Core with AWS Lambda (for Microsoft Developers)

Image
Continuing to support Microsoft's .NET Core initiative, Amazon Web Services Inc. (AWS) this week opened up more .NET Core options for working with AWS Lambda, a service that facilitates serverless, event-driven computing. .NET Core is Microsoft's modernization of the ageing, Windows-only .NET Framework, taking it open source and cross-platform in a more modularized approach. The company has advised developers that .NET Core is the future and recommends it for all new development projects because it will be getting new features and functionality going forward, while .NET Framework will be relegated to security and maintenance updates. In announcing a new  Amazon.Lambda.RuntimeSupport  library, AWS made it possible for developers to create their own custom runtimes in order to use more versions of .NET Core beyond the version that's currently built-in to the AWS Lambda service. Previously, developers could only use Long Term Support (LTS) versions of .NET Core
Read more

Working with AWS Fargate (Lots of fun)

Image
AWS Fargate is being hailed as a game-changer in the world of containerized microservices. In much the same way that the cloud has freed developers from managing the VM infrastructure, the Fargate service abstracts and automates the launching and orchestration of Docker or Kubernetes containers—letting developers take full advantage of the latest in cloud-native app architectures without worrying about task networking, scaling, and other behind-the-scenes processes. This blog describes the Fargate service and how it fits into the container ecosystem. Containers and Their Benefits According to  TechTarget  “[c]ontainers are packages that rely on virtual isolation to deploy and run applications that access a shared operating system (OS) kernel without the need for virtual machines (VMs).” The container image statically describes everything needed to run an application: code, runtime OS, system tools, system libraries and settings. During runtime the container engine reliably e
Read more

Azure to AWS services comparison/migration

Image
This article helps you understand how Amazon Web Services (AWS) compare to Microsoft Azure services. Whether you are planning a multicloud solution with Azure and AWS, or migrating Azure to AWS, you can compare the IT capabilities of Azure and AWS services in all categories. AWS and Azure for multicloud solutions As the leading public cloud platforms, AWS and Azure each offer businesses a broad and deep set of capabilities with global coverage. Yet many organizations choose to use both platforms together for greater choice and flexibility, as well as to spread their risk and dependencies with a multicloud approach. Consulting companies and software vendors might also build on and use both AWS and Azure, as these platforms represent most of the cloud market demand.  AWS and Azure are adding more services everyday so i will try to keep the content current. Marketplace Area             AWS service Azure service Description Marketplace AWS Marketplace Azure Marketpl
Read more