<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Serverless on The Coders Blog</title><link>https://thecodersblog.com/tag/serverless/</link><description>Recent content in Serverless on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 22:26:31 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/serverless/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloudflare: Introducing Dynamic Workflows for Durable Execution</title><link>https://thecodersblog.com/cloudflare-dynamic-workflows-2026/</link><pubDate>Wed, 06 May 2026 22:26:31 +0000</pubDate><guid>https://thecodersblog.com/cloudflare-dynamic-workflows-2026/</guid><description>&lt;p&gt;Imagine an AI agent pipeline that needs to dynamically spin up new code for each tenant, or a CI/CD system that must execute user-supplied scripts in a secure sandbox. The bottleneck isn&amp;rsquo;t just executing code; it&amp;rsquo;s executing it &lt;em&gt;durably&lt;/em&gt;, &lt;em&gt;tenant-specifically&lt;/em&gt;, and with &lt;em&gt;rapid instantiation&lt;/em&gt;. This is precisely the problem Cloudflare Dynamic Workflows aims to solve.&lt;/p&gt;
&lt;h3 id="the-core-problem-unreliable-slow-and-inflexible-dynamic-code-execution"&gt;The Core Problem: Unreliable, Slow, and Inflexible Dynamic Code Execution&lt;/h3&gt;
&lt;p&gt;Traditional serverless functions are excellent for stateless, event-driven tasks. However, when you need to execute code that&amp;rsquo;s not predefined, dynamically loaded at runtime, and requires persistent state or coordination across multiple steps, things get complicated. Containerization offers flexibility but suffers from slow boot times and higher overhead. For multi-tenant applications or scenarios involving AI agent execution, the need for an execution environment that&amp;rsquo;s fast, secure, durable, and adaptable is paramount.&lt;/p&gt;</description></item><item><title>AWS MCP Server is Now Generally Available: What You Need to Know</title><link>https://thecodersblog.com/aws-mcp-server-general-availability-2026/</link><pubDate>Wed, 06 May 2026 17:06:06 +0000</pubDate><guid>https://thecodersblog.com/aws-mcp-server-general-availability-2026/</guid><description>&lt;p&gt;Imagine your AI agent, trained on vast datasets, suddenly needing to provision a new S3 bucket or troubleshoot a flaky EC2 instance. How does it securely, and reliably, interact with your cloud infrastructure? This is the gap the AWS MCP Server, now generally available, aims to bridge. It promises to unlock powerful AI-driven automation, but demands a critical eye on its implementation.&lt;/p&gt;
&lt;h2 id="the-core-problem-ai-agents-without-cloud-access-are-limited"&gt;The Core Problem: AI Agents Without Cloud Access Are Limited&lt;/h2&gt;
&lt;p&gt;AI agents are increasingly sophisticated, capable of understanding complex requests and generating code. However, without a secure and authenticated channel to interact with real-world systems, their utility remains largely theoretical. Asking an AI to &amp;ldquo;create a VPC with public and private subnets&amp;rdquo; is one thing; enabling it to &lt;em&gt;actually&lt;/em&gt; execute the necessary AWS API calls is another. This is where the Model Context Protocol (MCP) server, and specifically the AWS MCP Server, enters the picture, offering AI agents authenticated access to over 15,000 AWS API operations.&lt;/p&gt;</description></item></channel></rss>