MonkeyCache

Apizr

11 Apr: Apizr v4.0, Refit based resilient api client – Highlights

The goal of Apizr v4.0 is still to get all ready to use for web api requesting, with the more resiliency we can, but without the boilerplate. It’s based on Refit, so what we can do with Refit could be done with Apizr too. But Apizr has more to offer, with at least: Working offline with cache management Handling errors with retry pattern and global catching Handling request priority Checking connectivity Tracing http traffic Handling authentication Mapping model with DTO Using Mediator pattern Using Optional pattern Anyway, this post is about changes only, but we published a series about Apizr already which you can find here. If you want to know how to get started or how to configure it, please read the brand new documentation: Anytime, feel free to browse code and samples too: LIBRAIRIES Apizr features are still provided by several NuGet packages, depending on what you need,…

apizr2

14 Jan: Apizr – Part 2: Resilient core features

This article is part of a series called Apizr: Apizr – Part 1: A Refit based web api client, but resilient Apizr – Part 2: Resilient core features (this one) Apizr – Part 3: More advanced features Apizr – Part 4: Requesting with Mediator pattern Apizr – Part 5: Requesting with Optional pattern   In Part 1, we’ve seen basic requesting features offered by Apizr. Some classic and well known request designs if you get some Refit skills, plus some built-in CRUD exclusive apis. In this Part 2, we’ll go through what exactly Apizr has to offer beyond its requesting main features, to reach our goal of something easily resilient. Here are some of its core features: Connectivity checking Authenticating Policing Prioritizing Caching Mapping Logging OPTIONSBUILDER While initializing, Apizr provides a fluent way to configure many things with something called OptionsBuilder. Each initialization approach comes with its OptionsBuilder optional parameter,…

apizr1_full

17 Dec: Apizr – Part 1: A Refit based web api client, but resilient

This article is part of a series called Apizr: Apizr – Part 1: A Refit based web api client, but resilient (this one) Apizr – Part 2: Resilient core features Apizr – Part 3: More advanced features Apizr – Part 4: Requesting with Mediator pattern Apizr – Part 5: Requesting with Optional pattern   Into this Apizr blog post series, I’ll try to demonstrate all features offered by the Apizr library, starting from core and going further with integration packages. Apizr project was motivated by this 2015 famous blog post about resilient networking with Xamarin. You should read it if you didn’t yet, because it’s old but still valid. My focus with Apizr was to address at least everything explained into this old article, which mean: Easy access to restful services Work offline with cache management Handle errors with retry pattern and global catching Handle request priority Check connectivity Fast…