Displaying 1 to 15 from 15 results

Polly - Polly is a

  •    CSharp

Polly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner.Polly targets .NET 4.0, .NET 4.5 and .NET Standard 1.1 (coverage: .NET Core, Mono, Xamarin.iOS, Xamarin.Android, UWP, WP8.1+).

awesome-chaos-engineering - A curated list of awesome Chaos Engineering resources.

  •    

A curated list of awesome Chaos Engineering resources. Chaos Engineering is the discipline of experimenting on a distributed system in order to build confidence in the system’s capability to withstand turbulent conditions in production. - Principles Of Chaos Engineering website.

cockatiel - A resilience and transient-fault-handling library that allows developers to express policies such as Backoff, Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback

  •    TypeScript

I recommend reading the Polly wiki for more information for details and mechanics around the patterns we provide. There are two events, onSuccess/onFailure, that are called when a call succeeds or fails. Note that onFailure only is called if a handled error is thrown.

Resilience4j - Fault tolerance library designed for Java8 and functional programming

  •    Java

Resilience4j is a lightweight fault tolerance library inspired by Netflix Hystrix, but designed for Java 8 and functional programming. Resilience4j provides higher-order functions (decorators) to enhance any functional interface, lambda expression or method reference with a Circuit Breaker, Rate Limiter, Retry or Bulkhead. You can stack more than one decorator on any functional interface, lambda expression or method reference. The advantage is that you have the choice to select the decorators you need and nothing else.




muxy - Chaos engineering tool for simulating real-world distributed system failures

  •    Go

Proxy for simulating real-world distributed system failures to improve resilience in your applications.Muxy is a proxy that mucks with your system and application context, operating at Layers 4, 5 and 7, allowing you to simulate common failure scenarios from the perspective of an application under test; such as an API or a web application.

rabbus - A tiny wrapper over amqp exchanges and queues 🚌 ✨

  •    Go

The rabbus package exposes a interface for emitting and listening RabbitMQ messages.

activist - activist.js is a drop-in library for resilience to network interference

  •    Javascript

activist.js is a standalone library for making your site resilient to unexpected network events. Activist comes in 2 versions, which offer a trade-off between how much work you need to do to add the library to your site, and how many of your users will be able to take advantage of the work. New browsers provide features that make the installation of activist.js as simple as adding a script tag to your home page, however this version of the library will only work for a small percentage of your user base (up-to-date chrome users). Activist also is packaged with a drop-in application cache manifst, which will extend the benefit to most users, but can require wider site changes.


goresilience - A library to improve the resilience of Go applications in an easy and flexible way

  •    Go

Well, this is not a circuit breaker library. Is true that Go has some good circuit breaker libraries (like sony/gobreaker, afex/hystrix-go or rubyist/circuitbreaker). But there is a lack a resilience toolkit that is easy to extend, customize and establishes a design that can be extended, that's why goresilience born. The aim of goresilience is to use the library with the resilience runners that can be combined or used independently depending on the execution logic nature (complex, simple, performance required, very reliable...).

CircuitBreaker.Net - Circuit Breaker pattern for .NET

  •    CSharp

CircuitBreaker.Net is an implementation of the Circuit Breaker pattern for .NET. This pattern can improve the stability and resiliency of your application, especially in SOAP, microservices and distributed environments. The pattern serves two main purposes: to isolate communication with third-party services, so that your application won't be affected by their fails. And to react to third-party services' fails: it could be a pause, throttling, fail-over, default behavior, etc. You can read about the pattern on MSDN or from Martin Fowler.

fuzz-monkey - Fuzzing tool written in Golang. Insane monkey not included.

  •    Go

Fuzz Monkey is a bit like chaos monkey only with more fur and instead of tearing down infrastructure like some kind of crazed baboon in a shoe shop, it carefully and surgically flings its poop at specific http endpoints. It ain't pretty, but it's damn sure fuzzy. or you can simply run the script and it will automatically root around for a file named fuzz-monkey.json.

vertx-in-action - Examples for the Manning "Vert.x in Action" book

  •    Java

These are the working examples for Vert.x in Action (ISBN 9781617295621) from Manning Publications Co and written by Julien Ponge. Readers of the book should directly open projects from subfolders: they are all independent.

ckt-breaker - Circuit breaker implementation in < 100 lines

  •    Javascript

Tiny circuit breaker implementation. Wrapped service must return Promise. If you are using this for one off scripts (eg. console apps), use process.exit(0) to exit the app.

resilient.js - Fault tolerant and reactive HTTP client for node.js and browsers

  •    Javascript

A reactive HTTP client for node.js and browsers designed for distributed systems, providing fault tolerance capabilities with transparent server fallback, dynamic server discovery (e.g: using Consul), request retry/backoff logic, optional client-side balancing based on empirical server latency and more... Provides a simple middleware-oriented programmatic API and featured command-line interface. It has been designed to be lightweight (just ~2K SLOC. 9KB gzipped) and dependency free.