A Refit-based HTTP client library for .NET that adds resilience patterns like retry, caching, authentication, and logging with minimal code.
Apizr is a .NET library that extends Refit to create resilient HTTP API clients. It solves the problem of building robust networking layers by automatically handling retries, caching, authentication, logging, and connectivity checks, reducing boilerplate code and improving application reliability.
.NET developers building mobile, desktop, or web applications that consume RESTful APIs and need reliable networking with offline support and error resilience.
Developers choose Apizr because it consolidates multiple resilience libraries (like Polly, Refit, and caching providers) into a single, easy-to-configure package, offering a declarative attribute-based API and seamless integration with the .NET ecosystem.
Refit based web api client management, but resilient (retry, connectivity, cache, auth, log, priority, etc...)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Seamlessly integrates Polly or Microsoft Resilience for automatic retry, circuit breaker, and timeout policies, reducing boilerplate error-handling code as shown in the README configuration examples.
Supports multiple cache providers like Akavache, MonkeyCache, and MS Extensions Caching, enabling offline operation and optimized network usage with configurable cache modes.
Uses attribute decorations and fluent configuration to define API behaviors with minimal code, allowing quick setup through DI or static builder approaches.
Includes authentication, logging, request prioritization via Fusillade, and file transfer management, covering common cross-cutting concerns in one package.
The README shows multiple steps, optional packages, and configuration choices (e.g., static vs. DI), which can be overwhelming for simple integrations or rapid prototyping.
Relies on Refit, Polly, and various integration packages, increasing project bloat and potential compatibility issues, especially in dependency-sensitive environments.
Requires familiarity with Apizr's attribute system, resilience pipelines, and integrated libraries, slowing initial adoption compared to lighter alternatives.