Apizr.Tools.NSwag 5.0.0-preview.1

Apizr

Refit based web api client, but resilient (retry, connectivity, cache, auth, log, priority...)

What

The Apizr project was motivated by this 2015 famous blog post about resilient networking.

Its main focus was to address at least everything explained into this article, meanning:

• Easy access to restful services
• Work offline with cache management
• Handle errors with retry pattern and global catching
• Handle request priority
• Check connectivity
• Fast development time
• Easy maintenance
• Reuse existing libraries

But also, some more core features like:

• Trace http traffic
• Handle authentication

And more integration/extension independent optional features like:

• Choose cache, log and connectivity providers
• Register it as an MS DI extension
• Map model with DTO
• Use Mediator pattern
• Use Optional pattern
• Manage file transfers

The list is not exhaustive, there�s more, but what we wanted was playing with all of it with as less code as we could, not worrying about plumbing things and being sure everything is wired and handled by design or almost.

Inspired by Refit.Insane.PowerPack, we wanted to make it simple to use, mixing attribute decorations and fluent configuration.

Also, we built this lib to make it work with any .Net Standard 2.0 compliant platform, so we could use it seamlessly from any kind of app, with or without DI goodness.

How

An api definition with some attributes:

[assembly:Policy("TransientHttpError")]
namespace Apizr.Sample
{
    [WebApi("https://reqres.in/"), Cache, Log]
    public interface IReqResService
    {
        [Get("/api/users")]
        Task<UserList> GetUsersAsync();

        [Get("/api/users/{userId}")]
        Task<UserDetails> GetUserAsync([CacheKey] int userId);

        [Post("/api/users")]
        Task<User> CreateUser(User user);
    }
}

An instance of this managed api:

// Define some policies
var registry = new PolicyRegistry
{
    {
        "TransientHttpError", 
        HttpPolicyExtensions
            .HandleTransientHttpError()
            .WaitAndRetryAsync(new[]
        {
            TimeSpan.FromSeconds(1),
            TimeSpan.FromSeconds(5),
            TimeSpan.FromSeconds(10)
        })
    }
};

// Get your manager instance
var reqResManager = ApizrBuilder.Current.CreateManagerFor<IReqResService>(
    options => options
        .WithPolicyRegistry(registry)
        .WithAkavacheCacheHandler());

And then you're good to go:

var userList = await reqResManager.ExecuteAsync(api => api.GetUsersAsync());

This request will be managed with the defined policies, data cached, http traces logged.

Apizr has a lot more to offer, just read the doc!

Where

Change Log

Managing (Core)

Project	Current	Upcoming
Apizr
Apizr.Extensions.Microsoft.DependencyInjection

Caching

Project	Current	Upcoming
Apizr.Extensions.Microsoft.Caching
Apizr.Integrations.Akavache
Apizr.Integrations.MonkeyCache

Handling

Project	Current	Upcoming
Apizr.Integrations.Fusillade
Apizr.Integrations.MediatR
Apizr.Integrations.Optional

Mapping

Project	Current	Upcoming
Apizr.Integrations.AutoMapper

Transferring

Project	Current	Upcoming
Apizr.Integrations.FileTransfer
Apizr.Extensions.Microsoft.FileTransfer
Apizr.Integrations.FileTransfer.MediatR
Apizr.Integrations.FileTransfer.Optional

Generating

Project	Current	Upcoming
Apizr.Tools.NSwag

Install the NuGet reference package of your choice:

• Apizr package comes with the static builder 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.Integrations.FileTransfer package enables file transfer management for static registration
• Apizr.Extensions.Microsoft.FileTransfer package enables file transfer management for extended registration
• Apizr.Integrations.FileTransfer.MediatR package enables file transfer management for mediation requests (requires MediatR integration and could work with Optional integration) using MediatR
• Apizr.Integrations.FileTransfer.Optional package enables file transfer management for mediation requests with optional result (requires MediatR integration and could work with Optional integration) using Optional.Async

Install the NuGet .NET CLI Tool package if needed:

• Apizr.Tools.NSwag package enables Apizr files generation by command lines (Models, Apis and Registrations) from an OpenApi/Swagger definition using NSwag

Apizr core package make use of well known nuget packages to make the magic appear:

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)