Digital Ocean Functions compared to Amazon Cloudfront Functions

Digital Ocean Functions
Versus
Amazon Cloudfront Functions

Features

Edge Features of Digital Ocean Functions compared to Amazon Cloudfront Functions
Digital Ocean FunctionsFeaturesAmazon Cloudfront Functions
Functions / Serverless
Go, Javascript, Php, PythonFunctions 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
New York, USA and Frankfurt, GermanyAvailability regionsAll POPs connected to your Cloudfront property
Default Memory (MB)128
Maximum Memory (MB)3008
Execution Time (ms)3,000
Maximum Execution Time (ms)900,000
Request Payload (MB)6
Response Payload (MB)6
Unsupported Paid Feature Supported Unknown

Descriptions


Digital Ocean Functions


Digital Ocean has earned users trust over the many years of service. Founded in 2011, and already traded publically on the New York Stock Exchange since 2021. Digital Ocean has a great blog with many useful articles, which is why they are so well known in the developer community.

Once the underdog, and now David turned Goliath, Digital Ocean offers it all and has truly grown into a major market player when it comes to cloud infrastructure on a global scale.

Digital Ocean Functions offers seamless database integration and offers support for a couple of unique features like unit testing for your Functions. Interestingly Digital Ocean is one of the first Functions providers who are verbal on which version of prograamming language they support. Some programming languages like Python are backward incompatible. DO’s Functions supports Python 3.

Noteworthy customers of Digital Ocean Functions are currently unknown.


Amazon Cloudfront Functions


Amazon Cloudfront Function introduces cloud computing to every CloudFront pop around the globe.

Amazon Cloudfront Functions differs from Amazon’s [email protected] because CloudFront’s servers have been located traditionally at the edges of Amazon’s gigantic global network of servers. This means CloudFront functions will run closer to the end-user than traditional Lambda’s, which usually run within customers' own VPN or behind loadbalancers.

With this change in approach, Amazon hopes to even further play into the serverless space that is to become the future of IaaS or Serverless as a Service.

Given Amazon’s massive reach and the tremendously popular CloudFront product, this will surely be a success going forward. Perhaps even replacing Amazon’s [email protected] in the long term?