The Databricks Engineering Team needed something smarter: a Layer 7, request-level load balancer that could react dynamically to real service conditions instead of relying on connection-level routing decisions.
why not use headless service and do client side loadbalancing at the microservice level?
Perhaps to have a fallback to default load-balancing. Assuming that not every service is written in scala and uses the same routing library.
why not use headless service and do client side loadbalancing at the microservice level?
Perhaps to have a fallback to default load-balancing. Assuming that not every service is written in scala and uses the same routing library.