Lokvin Wiki
Edit Page

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 20: Line 20:
 
* A service mesh like linkerd provides critical features to multi-service applications running at scale:
 
* A service mesh like linkerd provides critical features to multi-service applications running at scale:
 
# Baseline resilience: retry budgets, deadlines, circuit-breaking
 
# Baseline resilience: retry budgets, deadlines, circuit-breaking
  +
#
# Top-line service metrics: success rates, request volumes, and latencies.
 
# latency and failure tolerance: Failure- and latency-aware load balancing that can route around slow or broken service instances.
 
# Distributed tracing a la Zipkin and OpenTracing
 
# Service discovery: locate destination instances.
 
# Protocol upgrades: wrapping cross-network communication in TLS, or converting HTTP/1.1 to HTTP/2.0.
 
# Routing: route requests between different versions of services, failover between clusters, etc.
 

Please note that all contributions to the Lokvin Wiki are considered to be released under the CC-BY-SA

Cancel Editing help (opens in new window)