Shimo Framework • Gin • Echo • gRPC • … Background in Shimo Platform • All in Kubernetes • Ingress Controller • Stateless Deployment • Stateful Sets • … • All in Cloud • ECS • RDS • OSS occurs How do we manage our microservices? Traffic Management - Rate limiting/Circuit Breaker • Ingress Controller • Client/Server side interceptor Traffic Management - Canary Scaling • Based on Kubernetes

Nacos 生态 其中主要涉及到数据面的代理服务 Proxy，集群入口网关 Ingress、集群出口网关 Egress 以及核心 控制面 Istiod。各个组件的功能如下：  代理服务 Proxy 采用的 Lyft 公司开源的高性能 C++ 网络代理 Envoy，拦截业务的所有出入流 量。  入口网关 Ingress，作为集群的访问入口，控制着集群内部服务如何安全的暴露出去，并对所有 入口流量进行统⼀控制和观测。 入口流量进行统⼀控制和观测。  出口网关 Egress，作为集群的访问出口，控制着集群内部服务如何安全的访问外部服务。  核心控制面 Istio 负责对所有数据面的代理服务 （包括 Ingress、Egress 网关）下发服务发现 信息，流量治理配置，以及用于服务之间进行双向认证的 TLS 证书。 可以看出 Istiod 是微服务领域的集大成者，覆盖了服务发现、服务治理、认证鉴权和可观测，以无 服务网格时代的 Nacos 随着云原生技术的发展和微服务 2.0 架构的提出，很多公司正在尝试通过服务网格技术去解决微服 务 1.0 架构中的问题。在微服务架构 2.0 架构中，流量是通过 ingress 网关接入的，进入微服务 体系，与 1.0 架构不同的是引入了数据面 Envoy 和控制面 Istio，Envoy 以 Sidecar 模式与应用部 署在同⼀个 Pod 中，会劫持应用的进出流量，然后可以通过控制面

own logic ○ Asynchronous execution ○ Recurrening execution ○ Accesses its own data (user defined ingress) ○ Guaranteed single threaded execution ○ Supports optional asynchronous destruction logic Alternative: own logic ○ Asynchronous execution ○ Recurrening execution ○ Accesses its own data (user defined ingress) ○ Guaranteed single threaded execution ○ Supports optional asynchronous destruction logicBasic Overview:

ve-message-count> true ingress-timestamp>falseingress-timestamp> Settings 56 Address configured metrics plugin for the matching address. Default is true . Read more about metrics. enable-ingress-timestamp determines whether or not the broker will add its time to messages sent to the matching long message annotation named x-opt-ingress-time . For core messages (used by the core and OpenWire protocols) the broker will add a long property named _AMQ_INGRESS_TIMESTAMP . For STOMP messages the

ve-message-count> true ingress-timestamp>falseingress-timestamp> Settings 65 address but configured metrics plugin for the matching address. Default is true . Read more about metrics. enable-ingress-timestamp determines whether or not the broker will add its time to messages sent to the matching long message annotation named x-opt-ingress-time . For core messages (used by the core and OpenWire protocols) the broker will add a long property named _AMQ_INGRESS_TIMESTAMP . For STOMP messages the

ve-message-count> true ingress-timestamp>falseingress-timestamp> Address Model 60 The idea configured metrics plugin for the matching address. Default is true . Read more about metrics. enable-ingress-timestamp determines whether or not the broker will add its time to messages sent to the matching long message annotation named x-opt-ingress-time . For core messages (used by the core and OpenWire protocols) the broker will add a long property named _AMQ_INGRESS_TIMESTAMP . For STOMP messages the

ve-message-count> true ingress-timestamp>falseingress-timestamp> Address Model 60 The idea configured metrics plugin for the matching address. Default is true . Read more about metrics. enable-ingress-timestamp determines whether or not the broker will add its time to messages sent to the matching long message annotation named x-opt-ingress-time . For core messages (used by the core and OpenWire protocols) the broker will add a long property named _AMQ_INGRESS_TIMESTAMP . For STOMP messages the

ve-message-count> true ingress-timestamp>falseingress-timestamp> Settings 62 For example plugin for the matching address. Default is true . Read more about metrics. Settings 67 enable-ingress-timestamp determines whether or not the broker will add its time to messages sent to the matching long message annotation named x-opt-ingress-time . For core messages (used by the core and OpenWire protocols) the broker will add a long property named _AMQ_INGRESS_TIMESTAMP . For STOMP messages the

ve-message-count> true ingress-timestamp>falseingress-timestamp> Settings 64 For example plugin for the matching address. Default is true . Read more about metrics. Settings 69 enable-ingress-timestamp determines whether or not the broker will add its time to messages sent to the matching long message annotation named x-opt-ingress-time . For core messages (used by the core and OpenWire protocols) the broker will add a long property named _AMQ_INGRESS_TIMESTAMP . For STOMP messages the

ve-message-count> true ingress-timestamp>falseingress-timestamp> Address Model 57 The idea configured metrics plugin for the matching address. Default is true . Read more about metrics. enable-ingress-timestamp determines whether or not the broker will add its time to messages sent to the matching long message annotation named x-opt-ingress-time . For core messages (used by the core and OpenWire protocols) the broker will add a long property named _AMQ_INGRESS_TIMESTAMP . For STOMP messages the