Section compared to Amazon Lambda @ Edge

Section
Versus
Amazon Lambda @ Edge

Features

Edge Features of Section compared to Amazon Lambda @ Edge
SectionFeaturesAmazon Lambda @ Edge
Functions / Serverless
Not bound by either containers or ‘functions’,Functions supported languagesjavascript, go, C/++, .NET, Node.js, PHP, python, ruby
Worker.js Environment
Docker supportYes, through EC2 Container Registry (ECR)
Docker private registry
Kubernetes support
Managed Kubernetes
Availability regionsAll compute pops
Default Memory (MB)128
Maximum Memory (MB)128
Execution Time (ms)5,000
Maximum Execution Time (ms)30,000
Request Payload (MB)50
Response Payload (MB).04
Unsupported Paid Feature Supported Unknown

Descriptions


Section


Section.io is one of those great companies that has forseen the future and made sure it’s established it’s name 10 years from now.

Built by developers for developers (api-first, ci/cd etc etc) and integration with BGP routing will ensure you’ll have a smooth experience running your applications practically next to the end-user’s home.

What is so unique about Section is their ability to visualize your cloud application’s flow in internet terms. This gives users a fantastic feel with their applications' whereabouts and performance.

A partnership with Centurylink will guarantee their sucess as a scaleup.


Amazon Lambda @ Edge


Amazon Lambda at the Edge functions introduced serverless cloud computing to the masses as early as 2014.

Being the first with a massive user-base has set up Amazon for great success, it took a few years for competitors to offer similar functionality and to actually call the FaaS space a new chapter in cloud compute in general.

Amazon’s [email protected] is Amazon’s first Edge Compute product, however Amazon recently released CloudFront Functions, which brings the compute a lot closer to the end-user.

With Amazon’s gigantic scale, a shift has started with companies that are on the AWS platform to move more and more of their infrastructure to serverless.