<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Service-Mesh on PAUL'S BLOG</title><link>https://paulyu.dev/tags/service-mesh/</link><description>Recent content in Service-Mesh on PAUL'S BLOG</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 14 Dec 2022 07:00:00 -0700</lastBuildDate><atom:link href="https://paulyu.dev/tags/service-mesh/index.xml" rel="self" type="application/rss+xml"/><item><title>Service Mesh Considerations</title><link>https://paulyu.dev/article/service-mesh-considerations/</link><pubDate>Wed, 14 Dec 2022 07:00:00 -0700</pubDate><guid>https://paulyu.dev/article/service-mesh-considerations/</guid><description>&lt;p&gt;&amp;ldquo;Build microservices&amp;rdquo;, they said&amp;hellip; &amp;ldquo;it&amp;rsquo;ll be fun&amp;rdquo;, they said&amp;hellip;&lt;/p&gt;
&lt;p&gt;There are many reasons why you would want to deploy a solution based on the &lt;a href="https://microservices.io/patterns/microservices.html"&gt;microservices architectural pattern&lt;/a&gt;, but it comes at a cost. More microservices means more deployments to manage, more microservices to connect, more microservices to secure&amp;hellip; yeah, it gets complex real quick.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re just getting started with microservices or have a small number of microservices deployed, you may have heard of the term &amp;ldquo;service mesh&amp;rdquo;, but not needed one yet.&lt;/p&gt;</description></item></channel></rss>