<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Event on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/event/</link><description>Recent content in Event on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Fri, 17 Feb 2023 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/event/atom.xml" rel="self" type="application/rss+xml"/><item><title>Transforming the Operations System with an Event Bus</title><link>https://www.chenshaowen.com/en/blog/transform-ops-system-using-event-bus.html</link><pubDate>Fri, 17 Feb 2023 00:00:00 +0000</pubDate><atom:modified>Fri, 17 Feb 2023 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/transform-ops-system-using-event-bus.html</guid><description>1. An Operations Service System That Has Piled Up Beyond Repair Developing a corresponding operations service for a clear operations need, so that operations and business users can use it, is entirely reasonable. But if you are satisfied with only that, the following situation easily appears:
Users constantly look for the entry point of each system, jumping back and forth between systems, busy hunting for buttons and copying parameters.</description><dc:creator>WeChat Official Account</dc:creator><category>Operations System</category><category>PaaS</category><category>Platform</category><category>Event</category><category>Architecture</category><category>Thoughts</category><category>Event-Driven</category><category>Learning</category><category>Automation</category></item></channel></rss>