Dev digest · 2026-10-24
1. AWS Introduces Lambda Web Functions for Node.js Applications
AWS recently introduced Lambda Web Functions, allowing developers to run Node.js web applications using frameworks such as Express and Hono directly on Lambda, with support for concurrent requests and response streaming. Lambda Web Functions currently support only Node.js, while other languages remain available through traditional Lambda functions, and the service is currently available in five regions.
Read source ↗Source evidence
AWS recently introduced Lambda Web Functions, allowing developers to run Node.js web applications using frameworks such as Express and Hono directly on Lambda, with support for concurrent requests and response streaming.
AWS recently introduced Lambda Web Functions , allowing developers to run Node.js web applications using frameworks such as Express and Hono directly on Lambda, with support for concurrent requests and response streaming.
Evidence source ↗
Lambda Web Functions currently support only Node.js, while other languages remain available through traditional Lambda functions, and the service is currently available in five regions.
Lambda Web Functions currently support only Node.js; other languages, including Python, Java, and .NET, remain available through traditional Lambda functions.
Evidence source ↗
The service is currently available in five regions: Northern Virginia, Ohio, Oregon, Tokyo, and Ireland.
Evidence source ↗
Today, Lambda Web Functions supports the Node.js runtime.
Evidence source ↗
2. Bringing post-quantum cryptography to geographically fenced key management
Cloudflare launched a post-quantum geographically restricted key manager in closed beta to support its Data Localization Suite, with general availability planned for Q1 2027. The system utilizes a hybrid ML-KEM-768 and X25519 protection scheme, combining NIST-standard post-quantum cryptography with classical components.
Read source ↗Source evidence
Cloudflare launched a post-quantum geographically restricted key manager in closed beta to support its Data Localization Suite, with general availability planned for Q1 2027.
Today, Cloudflare is launching a post-quantum geographically restricted key manager in support of our Data Localization Suite (DLS) in closed beta.
Evidence source ↗
While general availability (GA) is planned for Q1 2027, today’s launch is an important milestone on our journey to support our customers’ data sovereignty goals
Evidence source ↗
The system utilizes a hybrid ML-KEM-768 and X25519 protection scheme, combining NIST-standard post-quantum cryptography with classical components.
Cloudflare therefore uses hybrid ML-KEM-768 and X25519 protection with two kinds of keys, out of which ML-KEM-768 is a NIST standard that also opens doors to highly sensitive customers.
Evidence source ↗
Its key-encapsulation mechanism (KEM) combines ML-KEM-768 with X25519 , while HKDF -SHA-256 provides key derivation and AES-256-GCM provides authenticated encryption.
Evidence source ↗
3. How Commerce.com and Cloudflare are getting storefronts ready for AI agents
Cloudflare launched an edge implementation of WebMCP in beta during August to help AI agents interact with online storefronts reliably. Commerce.com uses Cloudflare to run nearly 100,000 domains and integrated WebMCP alongside its server-side Model Context Protocol. WebMCP remains an experimental browser proposal in early preview rather than a stable, broadly available browser standard.
Read source ↗Source evidence
Cloudflare launched an edge implementation of WebMCP in beta during August to help AI agents interact with online storefronts reliably.
In August, we launched edge implementation of WebMCP in beta.
Evidence source ↗
Commerce.com uses Cloudflare to run nearly 100,000 domains and integrated WebMCP alongside its server-side Model Context Protocol.
Commerce.com , a flexible commerce platform built for the age of AI, already uses Cloudflare to run their almost 100,000 domains.
Evidence source ↗
WebMCP also works side by side with our server-side MCP , and together they cover the different ways people shop with agents.
Evidence source ↗
WebMCP remains an experimental browser proposal in early preview rather than a stable, broadly available browser standard.
WebMCP is still an experimental proposed browser standard in early preview
Evidence source ↗
4. Google’s Data Agent Kit Reaches General Availability
Google announced general availability of Data Agent Kit on October 1, 2026, after its preview period. The kit works with third-party coding agents and has no additional kit fee, but the Google Cloud services used by an agent are billed at standard rates. With the general availability release, the company added support for BigQuery Graph, Bigtable, and Managed Service for Apache Spark.
Read source ↗Source evidence
Google announced general availability of Data Agent Kit on October 1, 2026, after its preview period.
Google recently made Data Agent Kit generally available , moving it out of the preview it ran through the summer.
Evidence source ↗
Today, Google Cloud Data Agent Kit is generally available.
Evidence source ↗
October 1, 2026 Arun Nair Product Manager, Google
Evidence source ↗
The kit works with third-party coding agents and has no additional kit fee, but the Google Cloud services used by an agent are billed at standard rates.
It is free, it is open source, and it installs into coding agents Google does not own.
Evidence source ↗
Data Agent Kit is included at no additional cost; you pay standard pricing only for the Google Cloud services your agent uses.
Evidence source ↗
With the general availability release, the company added support for BigQuery Graph, Bigtable, and Managed Service for Apache Spark.
With the GA release, the company adds BigQuery Graph, Bigtable, and Managed Service for Apache Spark.
Evidence source ↗
With GA, we are adding support for BigQuery Graph , Bigtable , and Managed Service for Apache Spark access to your open Lakehouse
Evidence source ↗
5. Cloudflare Reports Over 100 TB in Fleet-Wide RAM Savings from Consistent Hashing Changes
Cloudflare reports that optimizing consistent hashing in its Pingora Backend Router reclaimed more than 100 TB of RAM across its global deployment, rather than on one server. For its workload, the team reduced hashes per backend by about 90% based on distribution and collision analysis. The old and new rings ran alongside each other during a staged, data-center-scoped rollout to control cache churn and origin traffic.
Read source ↗Source evidence
Cloudflare reports that optimizing consistent hashing in its Pingora Backend Router reclaimed more than 100 TB of RAM across its global deployment, rather than on one server.
Cloudflare recently documented how it reduced the memory footprint of its internal load-balancing service by more than 100 TB by optimizing the Rust implementation of consistent hashing in pingora-ketama.
Evidence source ↗
100TB of RAM globally
Evidence source ↗
For its workload, the team reduced hashes per backend by about 90% based on distribution and collision analysis.
The changes compacted hash-ring entries and used statistical analysis of hash distribution and collision rates to reduce the number of hashes per backend by about 90% while preserving load-balancing accuracy.
Evidence source ↗
decrease the number of hashes we were generating for each server by 90%
Evidence source ↗
The old and new rings ran alongside each other during a staged, data-center-scoped rollout to control cache churn and origin traffic.
The new implementation was rolled out gradually alongside the existing ring to limit cache churn and origin traffic spikes.
Evidence source ↗
progressively larger groups of data centers
Evidence source ↗
Discussion