Have a #microservices, but don't want to introduce a #servicemesh?
- Want circuit breaking? github.com/Netflix/Hystrix solves it for you
- Want a gateway service? github.com/Netflix/zuul got you covered
- Standardize #RPC calls? github.com/Netflix/ribbon is out there
(1/n)
- Service discovery? github.com/Netflix/eureka, github.com/hashicorp/cons… and a few other proven projects
- Tracing? github.com/openzipkin/bra… and a few others
- Metrics? github.com/Netflix/specta…, github.com/prometheus and a few others.
(2/n)
A pattern which you would notice here is that, a lot of tools would end up re-implementing what a service mesh would do for you, as one thing complements the other. (3/n)
You WOULD need tracing/monitoring/circuit-breaking/load-balancing and the other lot of features which would be required if you have more than a couple of hundreds/thousands of #microservices. (4/n)
Now should you go with a #servicemesh/go with individual projects to achieve this depends on the team & how they draw their pro's and con's on either of the choices. Lock-in to a specific service mesh/having a more granular approach to things and have a plug and play setup (5/5)
Share this Scrolly Tale with your friends.
A Scrolly Tale is a new way to read Twitter threads with a more visually immersive experience.
Discover more beautiful Scrolly Tales like this.