Proxy Based Service Mesh

  • service discovery by configuring the software defined network to resolve host name “service1” to itself
  • load balancing by evenly distributing incoming requests to available service instances
  • delay a percentage of requests to observe the effects of increasing that service’s latency on the distributed system, make sure the system as a whole can handle it
  • fail a percentage of the incoming requests with random error codes and make sure the system can survive that.

--

--

--

Lead Architect at LiquidShare, building a cloud native, blockchain enabled, financial services SaaS platform.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Scrum should work for you. Don’t work for scrum.

Configure SonarQube for SpringBoot Project

Understanding Mixins in TypeScript

My Best Stories

Safaricom MPesa outage incident report / postmortem[fictional]

Error validating regions: MissingEndpoint: ‘Endpoint’ configuration is required for this service

Observations of High-Performing Engineering Teams

Advanced Commands for Middle-Level Linux Users

Advanced Commands for Middle Level Linux Users

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Emil Kirschner

Emil Kirschner

Lead Architect at LiquidShare, building a cloud native, blockchain enabled, financial services SaaS platform.

More from Medium

Rolling updates & rollbacks in Deployments (Kubernetes)

StreamNative Pulsar Operator Tutorial Part 2

Kubernetes Probes: Startup, Liveness, Readiness

Kubernetes or other Container Orchestrators: Select the right one for your applications