<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>异步 on Jeanphilo Blog</title><link>https://shio-chan-dev.github.io/jeanblog/zh/tags/%E5%BC%82%E6%AD%A5/</link><description>Recent content in 异步 on Jeanphilo Blog</description><generator>Hugo -- 0.159.2</generator><language>zh-cn</language><lastBuildDate>Sat, 24 Jan 2026 15:29:20 +0800</lastBuildDate><atom:link href="https://shio-chan-dev.github.io/jeanblog/zh/tags/%E5%BC%82%E6%AD%A5/index.xml" rel="self" type="application/rss+xml"/><item><title>为什么事件驱动架构能提升可扩展性</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/event-driven-scalability/</link><pubDate>Sat, 24 Jan 2026 15:29:20 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/architecture/event-driven-scalability/</guid><description>解释事件驱动架构的扩展优势、适用场景与工程取舍。</description></item><item><title>什么时候使用异步通信：场景、收益与代价</title><link>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/async-communication-when/</link><pubDate>Sat, 24 Jan 2026 11:20:31 +0800</pubDate><guid>https://shio-chan-dev.github.io/jeanblog/zh/dev/distributed/async-communication-when/</guid><description>解释同步/异步通信的取舍，并给出适用场景与落地建议。</description></item></channel></rss>