<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Caching on Euijun's Personal Blog</title><link>https://elbanic.github.io/tags/caching/</link><description>Recent content in Caching on Euijun's Personal Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 13 May 2026 17:32:42 +0900</lastBuildDate><atom:link href="https://elbanic.github.io/tags/caching/index.xml" rel="self" type="application/rss+xml"/><item><title>「Agentic AI Dev Note」 Developing and Operating Agents in a Distributed Systems</title><link>https://elbanic.github.io/posts/develop-and-operating-agents-in-a-distributed-environment/</link><pubDate>Wed, 13 May 2026 17:32:42 +0900</pubDate><guid>https://elbanic.github.io/posts/develop-and-operating-agents-in-a-distributed-environment/</guid><description>&lt;p&gt;We imagine it like this: a user sends a request to an Agent, an Agent floating somewhere processes the request, and returns the result. In the big picture, this is correct. However, a real distributed environment is not quite this simple.&lt;/p&gt;
&lt;p&gt;When a request comes in, a container is provisioned, the Agent inside it processes the request, and if it remains idle for a certain period, the container is destroyed. The next request might be received by a completely different container. This is a mechanism for the scalability and efficiency of a distributed system. If traffic increases, containers must be scaled up; if it decreases, they must be scaled down.&lt;/p&gt;</description></item></channel></rss>