<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Edge-Computing on Danilo Falcão da Silva</title><link>https://falcao.org/tags/edge-computing/</link><description>Recent content in Edge-Computing on Danilo Falcão da Silva</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 20 Jun 2026 12:30:00 -0300</lastBuildDate><atom:link href="https://falcao.org/tags/edge-computing/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloudflare's Agentic Cloud: The Infrastructure Play Nobody Is Talking About</title><link>https://falcao.org/posts/cloudflare-agentic-cloud-infrastructure-nobody-talking/</link><pubDate>Sat, 20 Jun 2026 12:30:00 -0300</pubDate><guid>https://falcao.org/posts/cloudflare-agentic-cloud-infrastructure-nobody-talking/</guid><description>&lt;p>Cloudflare spent a week in April shipping things and then called
the result &amp;ldquo;Cloud 2.0 — the agentic cloud.&amp;rdquo; That is a big claim,
and my first reaction to big claims from infrastructure vendors is
to look for the part they are not putting in the headline. The
marketing was about agents. The interesting part is the compute
model underneath it, and almost nobody is talking about that.&lt;/p>
&lt;p>The argument they are making is actually sound, which is rare. The
cloud we have was built for the smartphone era. One app serves many
users. You provision a fleet, you put it behind a load balancer,
you scale horizontally, and the whole shape assumes a many-to-one
relationship between users and processes. Agents break that shape.
An agent is one-to-one: one user, one agent, one task, often for
minutes at a stretch, holding state the whole time. That is a
genuinely different compute problem, and pretending it is just
&amp;ldquo;more web traffic&amp;rdquo; is how you end up with a bill that does not make
sense.&lt;/p></description></item></channel></rss>