<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Event-Driven-Architecture on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/event-driven-architecture/</link>
		<description>Recent content in Event-Driven-Architecture on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 11 Oct 2026 11:14:13 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/event-driven-architecture/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>What Is Serverless Computing and How Does It Work?</title>
				<link>https://www.compilemymind.com/posts/what-is-serverless-computing/</link>
				<pubDate>Sun, 11 Oct 2026 11:14:13 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/what-is-serverless-computing/</guid>
				<description>&lt;p&gt;A small photo-sharing application receives almost no traffic overnight. At lunchtime, a promotion sends thousands of people to it at once. Every uploaded image needs a thumbnail, but keeping a fleet of thumbnail servers running all day would waste money. Guessing the lunchtime peak would be fragile.&lt;/p&gt;&#xA;&lt;p&gt;This is the tension serverless computing is designed to relieve.&lt;/p&gt;&#xA;&lt;p&gt;Instead of choosing a server size and deciding how many copies should stay online, the team deploys code or a container and connects it to an event. An upload arrives, the platform starts enough execution capacity to process it, and that capacity can shrink when the work disappears.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
