<?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 Jinying Tech Blog</title>
    <link>https://chejinying.com/tech/tags/service-mesh/</link>
    <description>Recent content in Service-Mesh on Jinying Tech Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 24 May 2026 20:59:08 +0800</lastBuildDate>
    <atom:link href="https://chejinying.com/tech/tags/service-mesh/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Consul Overview</title>
      <link>https://chejinying.com/tech/posts/distributed-system/consul/</link>
      <pubDate>Sun, 24 May 2026 20:59:08 +0800</pubDate>
      <guid>https://chejinying.com/tech/posts/distributed-system/consul/</guid>
      <description>&lt;h2 id=&#34;background--motivation&#34;&gt;Background &amp;amp; Motivation&lt;/h2&gt;&#xA;&lt;p&gt;In traditional infrastructure, applications communicated via static IP addresses and hardware load balancers. As architectures evolved into dynamic microservices and cloud-native environments (like Kubernetes or auto-scaling VM groups), IP addresses became ephemeral. Services could start, stop, or move at any time.&lt;/p&gt;&#xA;&lt;p&gt;This created two major problems:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;strong&gt;Service Discovery&lt;/strong&gt;: How do services find each other when IPs constantly change?&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Security &amp;amp; Routing&lt;/strong&gt;: How do we secure communication (mTLS) and intelligently route traffic without hardcoding logic into every application?&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;HashiCorp introduced Consul to solve these challenges by providing a centralized registry and a unified control plane.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
