3 repositorios
Application-level patterns that use automatic retries to handle intermittent failures in logic.
Distinct from Resilient Infrastructure: Distinct from resilient infrastructure: focuses on the programmatic logic of retrying functions rather than system-wide availability architectures.
Explore 3 awesome GitHub repositories matching devops & infrastructure · Resilient Application Patterns. Refine with filters or upvote what's useful.
Tenacity is a Python retry library and fault tolerance framework designed to automatically re-execute failing functions based on custom conditions, wait intervals, and stop criteria. It provides a mechanism to apply retry logic to both synchronous functions and asynchronous coroutines. The library implements exponential backoff to increase delays between retries, helping to manage transient network failures and prevent the overloading of services. Its capabilities cover the definition of retry conditions based on exception types or return values, as well as the enforcement of duration limits
Handles intermittent failures in code by automatically retrying functions until they succeed or a limit is reached.
Deis is an open-source, self-hosted Platform-as-a-Service that deploys and manages containerized applications on a CoreOS cluster using a Heroku-inspired git push workflow. It accepts application code via git push, automatically builds a Docker image, and runs it as a container on the cluster, with systemd and etcd providing service discovery and configuration management. The platform provides a developer experience modeled after Heroku, with a command-line interface for creating, scaling, configuring, and monitoring applications. It hosts a private Git remote per application that triggers th
Optimizes application performance and increases workload productivity across cloud and edge environments.
ZIO is a functional effect system for the JVM that models asynchronous and concurrent programs as pure, composable values with typed error handling and dependency injection. Its core identity is built on fiber-based concurrency, where lightweight, non-blocking fibers execute millions of concurrent tasks with structured lifecycle management, and a dual-channel error model that separates expected business failures from unexpected system defects at compile time. The system provides effect-typed dependency injection through a layer-based dependency graph, pull-based reactive stream processing with
Provides application-level patterns that use automatic retries to handle intermittent failures in logic.