Skip to main content

A Sample On HttpClientFactory Implementation Using Named Clients Technique In .Net Core Application

An Overview On Named Clients:

  • In HttpClientFactory, the Named Clients technique is useful when an application has a requirement to consume multiple external API's.
  • In the Named Client approach HttpClienFactory produces the HttpClient object specific to the domain.
  • So if our requirement to consume multiple external domains then HttpClientFactory generates HttpClient object per domain based on their registration in a startup.cs file.
  • So each external API domain needs to be registered in the startup.cs file with a specific 'Name' to that HttpClient.
  • This name will be passed to HttpClientFactory to produce a HttpClient object with the specified configuration in the startup.cs file
  • Here we have a configuration object to set time out for the expiration of the HttpClient object.

Click here to learn more about an overview of HttpClientFactory

Basic Implementation Sample On HttpClientFactory Using HttpRequestMessage Object

Test 3rd Party API's:

So to understand and implement a sample on HttpClientFactory using the named technique we need to have external APIs. So were are going to use freely hosted rest APIs for a developer to use and learn like below:
JSONPlaceholder:
https://jsonplaceholder.typicode.com/

Dummy Rest API:
http://dummy.restapiexample.com/

Create A .Net Core Sample:

Let's create a .net core sample web API project that will consume the external APIs. We can use IDE like Visual Studio 2019(VS that supports 3.0 plus .net core) Or Visual Studio Code.

Register Named HttpClients:

  • On registering HttpClient will specify a name to the HttpClient. Along with specifying the name of HttpClient, we can also specify some configuration like 'BaseAddress', 'DefaultRequestHeaders', 'DefaultRequestVerion', 'Timeout'. 
  • 'BaseAddress' means domain of the third-party, API we need to consume, if specify the 'BaseAddress' on registering HttpClient then we no need to specify the domain or fully qualified URL at the Controller on making an API call.
  • 'DefaultRequestHeaders' we also can configure any default headers that need to specify on making an API call. If we want we can specify the header in controllers also, but headers will override these 'DefaultRequestHeaders'.
  • 'TimeOut' to specify the lifetime of the HttpClient. Means HttpClient will not be destroyed immediately after serving request it will live up to lifetime specified to utilize the server resource efficiently.
Let's now register HttpClients by names in Startup.cs file as follow:
Startup.cs:
public void ConfigureServices(IServiceCollection services)
{
	services.AddControllers();
	services.AddHttpClient("DummyRestApi",(client)=>{
		client.BaseAddress = new Uri("http://dummy.restapiexample.com");
	});
	services.AddHttpClient("JsonPlaceholder",(client) => {
    client.BaseAddress = new Uri("https://jsonplaceholder.typicode.com");
	});
}
In the above code snippet, we can observe HttpClient has been registered with names like 'DummyRestApi', 'JsonPacleholder'. Configured both clients with respective API domains. 

Inject  IHttpClientFactory Service:

To consume System.Net.Http.IHttpClientFactory service we need to inject it. So as the first step let's create a TestController.cs file and inject IHttpClienFactory into it.
Controllers/TestController.cs:
using System.Net.Http;
using Microsoft.AspNetCore.Mvc;

namespace NamedFacotryApp.Controllers
{
    [ApiController]
    [Route("[controller]")]
    public class TestController : ControllerBase
    {
        private readonly IHttpClientFactory _httpClientFacotry;
        public TestController(IHttpClientFactory httpClientFactory)
        {
            _httpClientFacotry =httpClientFactory;
        }
    }
}

Get Action Method:

Now we will create an HttpClient object from HttpClientFactory using registered HttpClient names with the predefined configuration that is in Startup.cs file. Since the domain of external API is already registered in Startup.cs file in the controller level on invoking a specific endpoint, we can provide a relative endpoint as input URL to the HttpRequestMessage object will be enough.

Let's install NewtonSoft.Json Nuget for effective serialization and deserialization of API JSON result.
CLI Command:

dotnet add package Newtonsoft.Json
PackageManager:

Install-Package Newtonsoft.Json
So first let's consume 'DummyRestAPI' and the endpoint looks as below.

So now let's create a model object to capture the JSON result from the external API in the above screenshot.

Now let's create an Employee model object as follows:
Models/Employee.cs:
using Newtonsoft.Json;

namespace NamedFacotryApp.Models
{
    public class Employee
    {
        [JsonProperty(PropertyName = "id")]
        public string Id { get; set; }

        [JsonProperty(PropertyName = "employee_name")]
        public string EmployeeName { get; set; }
        [JsonProperty(PropertyName = "employee_salary")]
        public string EmployeeSalary { get; set; }
        [JsonProperty(PropertyName = "employee_age")]
        public string EmplyeeAge { get; set; }
        [JsonProperty(PropertyName = "profile_image")]
        public string ProfileImage { get; set; }
    }
}
Here we are using Newtonsoft.Json.JsonProperty attribute to match the properties with the external API response.

From the above image, we can observe a collection of employee data reside inside of another result object, so to serialize we need to create a new object that holds a collection of employees like in the image.
Models/DummyResult.cs:
using System.Collections.Generic;
using Newtonsoft.Json;

namespace NamedFacotryApp.Models
{
    public class DummyResult
    {
        [JsonProperty(PropertyName = "status")]
        public string Status { get; set; }

        [JsonProperty(PropertyName="data")]
        public List<Employee> Data { get; set; }
    }
}
Now we will see how we can create a HttpClient object from HttpClientFactory using the Named Client technique. Let's create an action method that fetches all employee records as follows:
Controllers/TestController.cs:
using System.Collections.Generic;
using System.Net.Http;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;
using NamedFacotryApp.Models;
using Newtonsoft.Json;

namespace NamedFacotryApp.Controllers
{
    [ApiController]
    [Route("[controller]")]
    public class TestController : ControllerBase
    {
        private readonly IHttpClientFactory _httpClientFacotry;
        public TestController(IHttpClientFactory httpClientFactory)
        {
            _httpClientFacotry = httpClientFactory;
        }

        [HttpGet]
        [Route("all-employees")]
        public async Task<IActionResult> GetEmployees()
        {
            var request = new HttpRequestMessage(HttpMethod.Get, "/api/v1/employees");

            var client = _httpClientFacotry.CreateClient("DummyRestApi");

            var response = await client.SendAsync(request);

            if(!response.IsSuccessStatusCode)
            {
                return NoContent();
            }

            var responseString = await response.Content.ReadAsStringAsync();

            DummyResult result = JsonConvert.DeserializeObject<DummyResult>(responseString);
            return Ok(result);
        }
    }
}
  • (Line-26) "DummyRestApi" name of the HttpClient registered at the Startup.cs file. Using the same name we have to create a HttpClient object from the HttpClientFactory service.
  • (Line-24) Since we have registered our "DummyRestApi" domain as a configuration in Startup.cs file, here for HttpRequestMessage object passing partial API endpoint is enough. Because this HttpRequestMessage object will be used as an input parameter to the HttpClient object created by the "DummyRestApi" name which contains configurations like domain, default request headers, etc.
  • (Line-28) HttpClient object has an asynchronous method name 'SendAsync' which will trigger the API call. This method takes the input parameter as a HttpRequestMessage object which has all the configuration for the API call.
Now let's run the application and access the endpoint we have created which shows the output as below

For a better understanding of the named client technique lets create one more get action method that fetches data from 'JsonPalceHolder'(external free API). We will use the 'Post' endpoint from the 'JsonPlaceHolder'.The below image shows the basic idea of the 'Post' endpoint payload.
Let's create a model object that used to deserialize the JSON payload.
Models/Post.cs:
namespace NamedFacotryApp.Models
{
    public class Post
    {
        public int UserId { get; set; }
        public int Id { get; set; }
        public string Title { get; set; }
        public string Body { get; set; }
    }
}
Now let's do the implementation of the get action method for invoking external API call as follows:
Controllers/TestController.cs:
using System.Collections.Generic;
using System.Net.Http;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Mvc;
using NamedFacotryApp.Models;
using Newtonsoft.Json;

namespace NamedFacotryApp.Controllers
{
    [ApiController]
    [Route("[controller]")]
    public class TestController : ControllerBase
    {
        
        [HttpGet]
        [Route("user-posts")]
        public async Task<IActionResult> GetUserPosts()
        {
            var request = new HttpRequestMessage(HttpMethod.Get, "/posts");

            var client = _httpClientFacotry.CreateClient("JsonPlaceholder");

            var response = await client.SendAsync(request);

            if (!response.IsSuccessStatusCode)
            {
                return NoContent();
            }

            var responseString = await response.Content.ReadAsStringAsync();

            List<Post> result = JsonConvert.DeserializeObject<List<Post>>(responseString);

            return Ok(result);
        }
    }
}
(Line-21) Using 'JsonPlaceholder' name value creating the HttpClient object from the HttpClientFactory.

Now let's run the application and checks the output as below:

Hereby observing two endpoints that use the named client technique helps in creating the HttpClient object from the HttpClientFactory services.

Support Me!
Buy Me A Coffee PayPal Me

Wrapping Up:

Hopefully, I think this article delivered some useful information about the Named Client Technique Of HttpClientFactory. I love to have your feedback, suggestions, and better techniques in the comment section below.

Follow Me:

Labels:

Comments

  1. AnonymousMarch 8, 2021 at 10:40 PM

    This is great, step by step explanation.

    ReplyDelete

Post a Comment

Popular posts from this blog

Angular 14 Reactive Forms Example

In this article, we will explore the Angular(14) reactive forms with an example. Reactive Forms: Angular reactive forms support model-driven techniques to handle the form's input values. The reactive forms state is immutable, any form filed change creates a new state for the form. Reactive forms are built around observable streams, where form inputs and values are provided as streams of input values, which can be accessed synchronously. Some key notations that involve in reactive forms are like: FormControl - each input element in the form is 'FormControl'. The 'FormControl' tracks the value and validation status of form fields. FormGroup - Track the value and validate the state of the group of 'FormControl'. FormBuilder - Angular service which can be used to create the 'FormGroup' or FormControl instance quickly. Form Array - That can hold infinite form control, this helps to create dynamic forms. Create An Angular(14) Application: Let'
3 comments
Read more

.NET 7 Web API CRUD Using Entity Framework Core

In this article, we are going to implement a sample .NET 7 Web API CRUD using the Entity Framework Core. Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, and desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains programming functions that can be requested via HTTP calls either to fetch or update data for their respective clients. Some of the Key Characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build the REST full services. Install The SQL Server And SQL Management Studio: Let's install the SQL server on our l
3 comments
Read more

ReactJS(v18) JWT Authentication Using HTTP Only Cookie

In this article, we will implement the ReactJS application authentication using the HTTP-only cookie. HTTP Only Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing the JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-ONly cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use the authentication with HTTP-only JWT cookie then we no need to implement the custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To authenticate our client application with JWT HTTP-only cookie, I developed a NetJS(which is a node) Mock API. Check the GitHub link and read the document on G
3 comments
Read more

.NET6 Web API CRUD Operation With Entity Framework Core

In this article, we are going to do a small demo on AspNetCore 6 Web API CRUD operations. What Is Web API: Web API is a framework for building HTTP services that can be accessed from any client like browser, mobile devices, desktop apps. In simple terminology API(Application Programming Interface) means an interface module that contains a programming function that can be requested via HTTP calls to save or fetch the data for their respective clients. Some of the key characteristics of API: Supports HTTP verbs like 'GET', 'POST', 'PUT', 'DELETE', etc. Supports default responses like 'XML' and 'JSON'. Also can define custom responses. Supports self-hosting or individual hosting, so that all different kinds of apps can consume it. Authentication and Authorization are easy to implement. The ideal platform to build REST full services. Create A .NET6 Web API Application: Let's create a .Net6 Web API sample application to accomplish our
6 comments
Read more

Angular 14 State Management CRUD Example With NgRx(14)

In this article, we are going to implement the Angular(14) state management CRUD example with NgRx(14) NgRx Store For State Management: In an angular application to share consistent data between multiple components, we use NgRx state management. Using NgRx state helps to avoid unwanted API calls, easy to maintain consistent data, etc. The main building blocks for the NgRx store are: Actions - NgRx actions represents event to trigger the reducers to save the data into the stores. Reducer - Reducer's pure function, which is used to create a new state on data change. Store - The store is the model or entity that holds the data. Selector - Selector to fetch the slices of data from the store to angular components. Effects - Effects deals with external network calls like API. The effect gets executed based the action performed Ngrx State Management flow: The angular component needs data for binding.  So angular component calls an action that is responsible for invoking the API call.  Aft
8 comments
Read more

Angular 14 Crud Example

In this article, we will implement CRUD operation in the Angular 14 application. Angular: Angular is a framework that can be used to build a single-page application. Angular applications are built with components that make our code simple and clean. Angular components compose of 3 files like TypeScript File(*.ts), Html File(*.html), CSS File(*.cs) Components typescript file and HTML file support 2-way binding which means data flow is bi-directional Component typescript file listens for all HTML events from the HTML file. Create Angular(14) Application: Let's create an Angular(14) application to begin our sample. Make sure to install the Angular CLI tool into our local machine because it provides easy CLI commands to play with the angular application. Command To Install Angular CLI npm install -g @angular/cli Run the below command to create the angular application. Command To Create Angular Application ng new name_of_your_app Note: While creating the app, you will see a noti
5 comments
Read more

Unit Testing Asp.NetCore Web API Using xUnit[.NET6]

In this article, we are going to write test cases to an Asp.NetCore Web API(.NET6) application using the xUnit. xUnit For .NET: The xUnit for .Net is a free, open-source, community-focused unit testing tool for .NET applications. By default .Net also provides a xUnit project template to implement test cases. Unit test cases build upon the 'AAA' formula that means 'Arrange', 'Act' and 'Assert' Arrange - Declaring variables, objects, instantiating mocks, etc. Act - Calling or invoking the method that needs to be tested. Assert - The assert ensures that code behaves as expected means yielding expected output. Create An API And Unit Test Projects: Let's create a .Net6 Web API and xUnit sample applications to accomplish our demo. We can use either Visual Studio 2022 or Visual Studio Code(using .NET CLI commands) to create any.Net6 application. For this demo, I'm using the 'Visual Studio Code'(using the .NET CLI command) editor. Create a fo
7 comments
Read more

Part-1 Angular JWT Authentication Using HTTP Only Cookie[Angular V13]

In this article, we are going to implement a sample angular application authentication using HTTP only cookie that contains a JWT token. HTTP Only JWT Cookie: In a SPA(Single Page Application) Authentication JWT token either can be stored in browser 'LocalStorage' or in 'Cookie'. Storing JWT token inside of the cookie then the cookie should be HTTP Only. The HTTP-Only cookie nature is that it will be only accessible by the server application. Client apps like javascript-based apps can't access the HTTP-Only cookie. So if we use authentication with HTTP only JWT cookie then we no need to implement custom logic like adding authorization header or storing token data, etc at our client application. Because once the user authenticated cookie will be automatically sent to the server by the browser on every API call. Authentication API: To implement JWT cookie authentication we need to set up an API. For that, I had created a mock authentication API(Using the NestJS Se
Post a Comment
Read more

ReactJS(v18) Authentication With JWT AccessToken And Refresh Token

In this article, we are going to do ReactJS(v18) application authentication using the JWT Access Token and Refresh Token. JSON Web Token(JWT): JSON Web Token is a digitally signed and secured token for user validation. The JWT is constructed with 3 important parts: Header Payload Signature Create ReactJS Application: Let's create a ReactJS application to accomplish our demo. npx create-react-app name-of-your-app Configure React Bootstrap Library: Let's install the React Bootstrap library npm install react-bootstrap bootstrap Now add the bootstrap CSS reference in 'index.js'. src/index.js: import 'bootstrap/dist/css/bootstrap.min.css' Create A React Component 'Layout': Let's add a React component like 'Layout' in 'components/shared' folders(new folders). src/components/shared/Layout.js: import Navbar from "react-bootstrap/Navbar"; import { Container } from "react-bootstrap"; import Nav from "react-boot
Post a Comment
Read more

A Small Guide On NestJS Queues

NestJS Application Queues helps to deal with application scaling and performance challenges. When To Use Queues?: API request that mostly involves in time taking operations like CPU bound operation, doing them synchronously which will result in thread blocking. So to avoid these issues, it is an appropriate way to make the CPU-bound operation separate background job.  In nestjs one of the best solutions for these kinds of tasks is to implement the Queues. For queueing mechanism in the nestjs application most recommended library is '@nestjs/bull'(Bull is nodejs queue library). The 'Bull' depends on Redis cache for data storage like a job. So in this queueing technique, we will create services like 'Producer' and 'Consumer'. The 'Producer' is used to push our jobs into the Redis stores. The consumer will read those jobs(eg: CPU Bound Operations) and process them. So by using this queues technique user requests processed very fastly because actually
8 comments
Read more