<?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>Argo Events on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/argo-events/</link><description>Recent content in Argo Events on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Wed, 27 Mar 2024 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/argo-events/atom.xml" rel="self" type="application/rss+xml"/><item><title>Event-Driven Workflows with Argo Events</title><link>https://www.chenshaowen.com/en/blog/event-driven-workflow-using-argo-events.html</link><pubDate>Wed, 27 Mar 2024 00:00:00 +0000</pubDate><atom:modified>Wed, 27 Mar 2024 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/event-driven-workflow-using-argo-events.html</guid><description>1. How Argo Events Works The diagram above is from the official Argo Events website. An event processing system has three important parts:
Ingesting event sources, which corresponds to the Event Source Distributing events, which corresponds to the Event Sensor Consuming events, which corresponds to the Event Trigger The event messages are stored in the EventBus, which uses NATS by default.</description><dc:creator>微信公众号</dc:creator><category>Argo</category><category>Argo Events</category><category>Kubernetes</category><category>CICD</category><category>Event-Driven</category><category>Operations</category></item></channel></rss>