<?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>Jni on Mark 的滿紙方糖言</title>
    <link>https://blog.mygraphql.com/zh/tags/jni/</link>
    <description>Recent content in Jni on Mark 的滿紙方糖言</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh</language>
    <managingEditor>labile.zhu@gmail.com (Mark Zhu)</managingEditor>
    <webMaster>labile.zhu@gmail.com (Mark Zhu)</webMaster>
    <copyright>Mark Zhu ©2026, All Rights Reserved</copyright>
    <lastBuildDate>Sat, 27 Jul 2024 08:12:15 +0800</lastBuildDate>
    
        <atom:link href="https://blog.mygraphql.com/zh/tags/jni/index.xml" rel="self" type="application/rss+xml" />
    

      
      <item>
        <title>Envoy Mobile - 终端设备 Istio Sidecar 可行吗</title>
        <link>https://blog.mygraphql.com/zh/posts/cloud/envoy/envoy-mobile/</link>
        <pubDate>Sat, 27 Jul 2024 08:12:15 +0800</pubDate>
        <author>labile.zhu@gmail.com (Mark Zhu)</author>
        <atom:modified>Sat, 27 Jul 2024 08:12:15 +0800</atom:modified>
        <guid>https://blog.mygraphql.com/zh/posts/cloud/envoy/envoy-mobile/</guid>
        <description>&lt;p&gt;Service Mesh 要是做到全链路到终端设备，就可统一流量从终端设备到最底层服务的控制面。或可为服务治理、流量可视化、边缘计算的流量本地化、响应时间的优化提供帮助。从而提升服务的用户体验。Envoy Mobile 有机会成为终端设备的 Istio Sidecar。&lt;/p&gt;</description>
        
        <dc:creator>Mark Zhu</dc:creator>
        
        
        
        
          
            
              <category>envoy</category>
            
          
            
              <category>java</category>
            
          
            
              <category>jvm</category>
            
          
            
              <category>jni</category>
            
          
            
              <category>istio</category>
            
          
        
        
        
      </item>
      
      <item>
        <title>Imagine: jEnvoy = pid(Java &#43; Envoy) - 脑洞还是脑残</title>
        <link>https://blog.mygraphql.com/zh/posts/cloud/envoy/jenvoy/</link>
        <pubDate>Sun, 07 Jul 2024 03:12:15 +0800</pubDate>
        <author>labile.zhu@gmail.com (Mark Zhu)</author>
        <atom:modified>Sun, 07 Jul 2024 03:12:15 +0800</atom:modified>
        <guid>https://blog.mygraphql.com/zh/posts/cloud/envoy/jenvoy/</guid>
        <description>&lt;p&gt;&lt;img src=&#34;https://blog.mygraphql.com/zh/posts/cloud/envoy/jenvoy/index.assets/imagine-john-lennon.png&#34; alt=&#34;image-20240711235224239&#34;&gt;&lt;/p&gt;
&lt;h2 id=&#34;引&#34;&gt;引&lt;/h2&gt;
&lt;p&gt;人们想要 service mesh 的低代码服务网格，但同时对 CPU 资源消耗与服务延迟的增加忧心重重。于是出现了各种 Sidecar-Less。本文想像一个把 Envoy 嵌入 jvm，作为一个 Servlet Container 的设计，希望达到性能、资源效益、低代码服务网格的平衡。&lt;/p&gt;</description>
        
        <dc:creator>Mark Zhu</dc:creator>
        
        
        
        
          
            
              <category>envoy</category>
            
          
            
              <category>java</category>
            
          
            
              <category>jvm</category>
            
          
            
              <category>jni</category>
            
          
        
        
        
      </item>
      

    
  </channel>
</rss>
