Get started quickly and conquer three different distributed architecture calling schemes

Load balancer scheme

SpringCloud solution

Google's Isto grid scheme

Comparison of the three schemes

• Load balancer scheme

• Supports automatic expansion: not supported, requires operation and maintenance intervention

• Core components: Nginx, HaProxy, F5

• Application coupling degree: high

• Load balancing granularity:Independent process

• Communication efficiency (theoretical): depends on the specific product

• Communication mode: all, depends on the load balancing product

• The cost of upgrading the old system: easy and happy

• Recommended Scenario: Traditional Enterprise Application

• Spring Cloud Solution

• Support automatic expansion: support, service registration discovery

• Core components: Eureka,Nacos,Consul

• Application coupling degree: low

• Load balancing granularity: In-process

• Communication efficiency (theoretical): High

• Communication mode: all, default RESTful, support various RPC (DUBBO)

• Old system upgrade cost: barely usable

• Recommended scenarios: enterprise application transformation, Internet application products

• lsto service grid solution

• Support automatic expansion: support, service registration discovery

• Core components: k8s,Istio pilot-discovery,Envoy

• Application coupling: low

• Load balancing granularity: independent process

• Communication efficiency (theoretical): General

• Communication mode: default RPC(GRPC), extended support for RESTFul

• Old system upgrade cost: uncomfortable

• Recommended scenarios: cloud native and large-scale cloud infrastructure applications

Summary