<?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>ServiceMesh on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/servicemesh/</link><description>Recent content in ServiceMesh on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Sat, 05 Dec 2020 00:01:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/servicemesh/atom.xml" rel="self" type="application/rss+xml"/><item><title>One Canvas Covers DevOps, ServiceMesh, Serverless</title><link>https://www.chenshaowen.com/en/blog/a-canvas-cover-devops-servicemesh-serverless.html</link><pubDate>Sat, 05 Dec 2020 00:01:00 +0000</pubDate><atom:modified>Sat, 05 Dec 2020 00:01:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/a-canvas-cover-devops-servicemesh-serverless.html</guid><description>Many cloud native open source components start with the service and add visualization later. Today I had a brainstorm and went the opposite way: first the visual interaction, then the underlying design.
1. One Canvas Covers Half of Cloud Native Users only need one canvas. Define the Workflow, and they can roam freely across all kinds of fancy Cloud Native applications.</description><dc:creator>WeChat Official Account</dc:creator><category>Cloud Native</category><category>DevOps</category><category>ServiceMesh</category><category>Serverless</category><category>Thoughts</category></item></channel></rss>