| Subsystem | Spring Cloud Ecosystem | Service Mesh Ecosystem |
|---|---|---|
| Service Registry & Discovery | The development is simple and convenient, just a simple annotation. it supports different registries. It is easy for developers to set up a development environment locally to complete coding and debugging. | Based on the Service mechanism of K8s, and provides its own Registry to synchronize the Registry. The developer needs to understand Kubernetes and the development environment is not easy to set up. |
| Resilient & Fault tolerance | The official integration of Resilience4j provides a complete fault-tolerant mechanism. But the service needs to be integrated with the SDK. | By using the sidecar architecture, it is a non-intrusive fault tolerance mechanism, totally transparent for service. |
| Observability | Spring Cloud build-in, spring micro-meter, Zipkin, etc. All service-inside metrics, tracing, and logs can be collected easily, and through the JavaAetcgent instrument method, it’s completely transparent to developers. | Through the sidecar mechanism, it can monitor the ingress or egress communication. Without the observability inside the service, the service tracing could be incomplete. |
| Traffic scheduling | Spring Cloud only has a very basic traffic scheduling. for example, the load balancing is based on Ribbon (removed from the latest version) | More traffic scheduling schemes, canary deployment, blue and green can be done gracefully. |
Created
August 24, 2021 08:53
-
-
Save haoel/fc4109c1011e16b8aa97be33e9ac9f85 to your computer and use it in GitHub Desktop.
comparison
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment