https://github.com/svroonland/rezilience

ZIO-native utilities for making resilient distributed systems
https://github.com/svroonland/rezilience

bulkhead circuit-breaker fault-tolerance scala zio

Last synced: 3 days ago
JSON representation

ZIO-native utilities for making resilient distributed systems

• Host: GitHub
• URL: https://github.com/svroonland/rezilience
• Owner: svroonland
• License: apache-2.0
• Created: 2020-05-16T13:26:53.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2024-04-08T16:27:15.000Z (7 months ago)
• Last Synced: 2024-04-08T20:15:03.089Z (7 months ago)
• Topics: bulkhead, circuit-breaker, fault-tolerance, scala, zio
• Language: Scala
• Homepage: https://www.vroste.nl/rezilience
• Size: 2.37 MB
• Stars: 152
• Watchers: 5
• Forks: 13
• Open Issues: 15
• Metadata Files:
  • Readme: README.md
  • Funding: FUNDING.yml
  • License: LICENSE

Awesome Lists containing this project

README

        
# Rezilience

_Use and like this library? Consider [sponsoring](https://github.com/sponsors/svroonland) its ongoing development and maintenance_

`rezilience` is a ZIO-native collection of policies for making asynchronous systems more resilient to failures.

It is inspired by [Polly](https://github.com/App-vNext/Polly), [Resilience4J](https://github.com/resilience4j/resilience4j) and [Akka](https://doc.akka.io/docs/akka/current/common/circuitbreaker.html).

It consists of these policies:

* `CircuitBreaker`

* `Bulkhead`

* `RateLimiter`

* `Retry`

* `Timeout`

## Features / Design goals

* Type-safety: all errors that can result from any of the `rezilience` policies are encoded in the method signatures, so no unexpected RuntimeExceptions.

* Support for your own error types (the `E` in `ZIO[R, E, A]`) instead of requiring your effects to have `Exception` as error type

* Lightweight: `rezilience` uses only ZIO fibers and will not create threads or block

* Switchable at runtime with two transition modes

* Resource-safe: built on ZIO's `ZManaged`, any allocated resources are cleaned up safely after use. 

* Interrupt safe: interruptions of effects wrapped by `rezilience` policies are handled properly.

* Thread-safe: all policies are safe under concurrent use.

* ZIO integration: some policies take for example ZIO `Schedule`s and `rezilience` tries to help type inference using variance annotations

* Metrics: all policies (will) provide usage metrics for monitoring purposes

* Composable: policies can be composed into one overall policy

* Discoverable: no syntax extensions or implicit conversions, just plain scala 

## Documentation

[Documentation](https://svroonland.github.io/rezilience)

Further questions? Look for the `#rezilience` channel on the ZIO Discord: https://discord.gg/2ccFBr4

## Installation

[![Sonatype Nexus (Releases)](https://img.shields.io/maven-central/v/nl.vroste/rezilience_2.13)](https://repo1.maven.org/maven2/nl/vroste/rezilience_2.13/) [![Sonatype Nexus (Snapshots)](https://img.shields.io/nexus/s/nl.vroste/rezilience_2.13?server=https%3A%2F%2Foss.sonatype.org)](https://oss.sonatype.org/content/repositories/snapshots/nl/vroste/rezilience_2.13/)

Add to your build.sbt:

```scala

libraryDependencies += "nl.vroste" %% "rezilience" % ""

```

## Used by

If you are using this library and find it useful, please consider adding your company or project to the list below!