Refit based web api client, but resilient (retry, connectivity, cache, auth, log, priority...)
| Project | Current | V-Next |
|---|---|---|
| Apizr |  |
 |
| Apizr.Extensions.Microsoft.DependencyInjection |  |
 |
| Apizr.Extensions.Microsoft.Caching |  |
 |
| Apizr.Integrations.Akavache |  |
 |
| Apizr.Integrations.MonkeyCache |  |
 |
| Apizr.Integrations.Fusillade |  |
 |
| Apizr.Integrations.MediatR |  |
 |
| Apizr.Integrations.Optional |  |
 |
| Apizr.Integrations.AutoMapper |  |
 |
Install the NuGet package of your choice:
- Apizr package comes with the For and CrudFor static instantiation approach (which you can register in your DI container then)
- Apizr.Extensions.Microsoft.DependencyInjection package extends your IServiceCollection with AddApizr, AddApizrFor and AddApizrCrudFor registration methods
- Apizr.Extensions.Microsoft.Caching package brings an ICacheHandler method mapping implementation for MS Extensions Caching
- Apizr.Integrations.Akavache package brings an ICacheHandler method mapping implementation for Akavache
- Apizr.Integrations.MonkeyCache package brings an ICacheHandler method mapping implementation for MonkeyCache
- Apizr.Integrations.Fusillade package enables request priority management using Fusillade
- Apizr.Integrations.MediatR package enables request auto handling with mediation using MediatR
- Apizr.Integrations.Optional package enables Optional result from mediation requests (requires MediatR integration) using Optional.Async
- Apizr.Integrations.AutoMapper package enables auto mapping for mediation requests (requires MediatR integration and could work with Optional integration) using AutoMapper
Apizr core package make use of well known nuget packages to make the magic appear:
| Package | Features |
|---|---|
| Refit | Auto-implement web api interface and deal with HttpClient |
| Polly | Apply some policies like Retry, CircuitBreaker, etc... |
| Microsoft.Extensions.Logging.Abstractions | Delegate logging layer to MS Extensions Logging |
It also comes with some handling interfaces to let you provide your own services for:
- Caching with ICacheHandler, which comes with its default VoidCacheHandler (no cache), but also with:
- InMemoryCacheHandler & DistributedCacheHandler: MS Extensions Caching methods mapping interface (Integration package referenced above), meaning you can provide any compatible caching engine
- AkavacheCacheHandler: Akavache methods mapping interface (Integration package referenced above)
- MonkeyCacheHandler: MonkeyCache methods mapping interface (Integration package referenced above)
- Logging As Apizr relies on official MS ILogger interface, you may want to provide any compatible logging engine (built-in DebugLogger activated by default)
- Connectivity with IConnectivityHandler, which comes with its default VoidConnectivityHandler (no connectivity check)
- Mapping with IMappingHandler, which comes with its default VoidMappingHandler (no mapping conversion), but also with:
- AutoMapperMappingHandler: AutoMapper mapping methods mapping interface (Integration package referenced above)