Huabing Blog

路在脚下,心向远方

What Can Service Mesh Learn from SDN?

what is the relationship between Service Mesh and SDN — Is Service Mesh the next generation of SDN? What can Service Mesh learn from the experience of SDN? I’d like to share some of my own opinions in this article.

如何降低Istio服务网格中Envoy的内存开销

在Istio服务网格中,每个Envoy占用的内存也许并不算多,但所有sidecar增加的内存累积起来则是一个不小的数字。在进行商用部署时,我们需要考虑如何优化并减少服务网格带来的额外内存消耗。

Service Mesher Meetup 成都站:Service Mesh是下一代SDN吗?

从SDN看Service Mesh的发展

Service Mesh和SDN(Software Defined Network) 的架构非常相似,这两者都采用了软件对网络进行管理和控制,也都包含控制面和数据面的概念。那么Service Mesh和SDN有什么关系?Service Mesh是下一代的SDN吗? Service Mesh可以从SDN的发展历史中借鉴哪些经验?本文将就这些问题进行一一探讨。

Istio Pilot代码深度解析

在Istio架构中,Pilot组件属于最核心的组件,负责了服务网格中的流量管理以及控制面和数据面之间的配置下发。Pilot内部的代码结构比较复杂,本文中我们将通过对Pilot的代码的深入分析来了解Pilot实现原理。

Enhance Istio Distributed Tracing with OpenTracing

Part 2: Enable Async Messaging Tracing with OpenTracing

In this post, we will continue to use the eshop demo to explore how asynchronous messaging, specifically Kafka, can be traced in Istio service mesh with the help of Opentracing.

Enhance Istio Distributed Tracing with OpenTracing

Part 1: Implement Fine-grained Tracing with OpenTracing

While evolving towards a microservices architecture, the biggest change is that the monolith application has been divided into multiple independent processes(or services), as a result, a method call between software modules now becomes a remote procedure call go through multiple services. A client request usually goes through a couple of or even a dozen of services in a complex microservices system, which makes it really hard to figure out w

洞若观火:使用OpenTracing增强Istio的调用链跟踪

第二篇:如何利用Opentracing实现Kafka消息的调用跟踪

本文将接着上一篇继续介绍如何利用OpenTracing来对Kafka异步消息进行跟踪,并将异步消息的跟踪信息加入Istio/Envoy生成的分布式调用跟踪链中进行统一呈现。

洞若观火:使用OpenTracing增强Istio的调用链跟踪

第一篇:如何利用Opentracing实现方法级的细粒度跟踪

本文将介绍如何利用OpenTracing来增强Istio/Envoy缺省的调用链跟踪实现:如何利用Opentracing来实现跨进程边界的分布式调用上下文传递;以及在Istio/Envoy生成的分布式调用跟踪基础上实现方法级的细粒度调用跟踪。

Which One is the Right Choice for the Ingress Gateway of Your Service Mesh?

Kubernetes Ingress, Istio Gateway or API Gateway?

By default, in a Kubernetes cluster with the Istio service mesh enabled, services can only be accessed inside the cluster. However, some of the services may need to be exposed to the external network as well. Kubernetes and Istio provide a variety of means to get external traffic into your cluster including NodePort, LoadBalancer, Kubernetes Ingress and Istio Gateway. With all these options, which one should be the right choice for your service mesh running in production?

如何为服务网格选择入口网关?

Kubernetes Ingress, Istio Gateway还是API Gateway?

在启用了Istio服务网格的Kubernetes集群中,缺省情况下只能在集群内部访问网格中的服务,要如何才能从外部网络访问这些服务呢? Kubernetes和Istio提供了NodePort,LoadBalancer,Kubernetes Ingress,Istio Gateway等多种外部流量入口的方式,面对这么多种方式,我们在产品部署中应该如何选择?