<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>云中间件实战 on vishine</title><link>https://blog.vishine.top/series/%E4%BA%91%E4%B8%AD%E9%97%B4%E4%BB%B6%E5%AE%9E%E6%88%98/</link><description>Recent content in 云中间件实战 on vishine</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sat, 18 Apr 2026 13:00:00 +0800</lastBuildDate><atom:link href="https://blog.vishine.top/series/%E4%BA%91%E4%B8%AD%E9%97%B4%E4%BB%B6%E5%AE%9E%E6%88%98/index.xml" rel="self" type="application/rss+xml"/><item><title>多云中间件横向速查与跨环境隔离实战</title><link>https://blog.vishine.top/posts/multi-cloud-middleware-and-isolation/</link><pubDate>Sat, 18 Apr 2026 13:00:00 +0800</pubDate><guid>https://blog.vishine.top/posts/multi-cloud-middleware-and-isolation/</guid><description>做多云运维最容易的事就是把 AWS 那套思维原样搬到阿里云，然后在某次故障里发现选型完全错位。本文整理了一份 AWS↔阿里云中间件横向对照表，附上跨环境隔离强制 checklist 和高频运维命令速查，是我自己工作中反复回查的一份速记。</description></item></channel></rss>