基于应用无关缓存的服务网格软断路
Towards Soft Circuit Breaking in Service Meshes via Application-agnostic Caching
摘要:
服务网格排除了处理微服务间通信的代码,例如断路。断路致动目前限于“开/关”开关,即,跳闸的断路器将向调用微服务返回指示服务不可用的应用级错误。本文提出了一种软断路器执行器,它返回缓存的数据,而不是一个错误。如果组成微服务返回陈旧数据,而不是根本没有数据,则云应用程序的整体弹性将得到改善。虽然缓存被广泛用于服务Web服务流量,但它在微服务间通信中的使用却很少。微服务响应是高度动态的,这需要仔细选择自适应的生存时间缓存算法。我们通过两个实验来评估我们的方法。首先,我们使用一个专门的服务来量化流量减少和数据陈旧之间的权衡,从而确定算法配置,使数据陈旧率保持在3%或更低,同时减少高达30%的网络负载。其次,我们使用Google Cloud的微服务基准(称为Hipster Shop)来量化网络负载减少。我们的方法可以缓存大约80%的请求。结果表明,我们的方法的可行性和效率,这鼓励实施缓存作为断路执行器在服务网格。
英文摘要:
Service meshes factor out code dealing with inter-micro-service communication, such as circuit breaking. Circuit breaking actuation is currently limited to an "on/off" switch, i.e., a tripped circuit breaker will return an application-level error indicating service unavailability to the calling micro-service. This paper proposes a soft circuit breaker actuator, which returns cached data instead of an error. The overall resilience of a cloud application is improved if constituent micro-services return stale data, instead of no data at all. While caching is widely employed for serving web service traffic, its usage in inter-micro-service communication is lacking. Micro-services responses are highly dynamic, which requires carefully choosing adaptive time-to-life caching algorithms. We evaluate our approach through two experiments. First, we quantify the trade-off between traffic reduction and data staleness using a purpose-build service, thereby identifying algorithm configurations that keep data staleness at about 3% or less while reducing network load by up to 30%. Second, we quantify the network load reduction with the micro-service benchmark by Google Cloud called Hipster Shop. Our approach results in caching of about 80% of requests. Results show the feasibility and efficiency of our approach, which encourages implementing caching as a circuit breaking actuator in service meshes.
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。