Circuit breaker pattern: Hystrix is dead, what are you using now?

with netflix hystrix deprecated, our team is looking for a modern alternative for implementing the circuit breaker pattern. we heavily relied on it for preventing cascading failures in our distributed systems, and now we need to decide on a replacement. we're evaluating options like resilience4j for java, polly for .net, and gobreaker for golang. another path is to offload this to a service mesh like istio or linkerd, which provides circuit breaking at the infrastructure level. the debate is whether to keep this logic at the application layer, giving developers more granular control, or push it down to the infrastructure layer for consistency and reduced application code. what are you all using for circuit breaking in your current production systems? what are the pros and cons you've observed between application-level libraries and service mesh-provided functionality? we need something robust for high-throughput, low-latency services.