Skip to main content

Why To Use HttpClientFactory In .Net Core

HttpClient instance was used to invoke or consume the external rest API by clients like console applications or web applications.

What Is Socket?:

A Socket is a system communication protocol providing a communication channel over TCP connection.

In programming, terminology socket can be defined as the combination of Url and Port Number to make communication channels.

HttpClient Working Flow:

Let's assume that we have .Net Core application, which will consume an external API using HttpClient. The steps involved in communication are as follows:
  1. The user requests our application, in which we need to call an external API to serve results to the user.
  2. On receiving user request our application creates an instance of HttpClient.
  3. Next HttpClient looks for HttpRequestHandler object in the pool of HttpRequestHandlers. Then HttpClient picks up one of the HttpRequestHandler objects and gives all input information like Url, payload, tokens, etc to make an external API call.
  4. Then HttpRequestHandler looks for Port Number on the server system. Then HttpRequestHandler grabs the Port Number and opens a Web Socket to open a communication channel.
  5. On successfully establishing the communication channel, the external API response will be delivered to the user who requested our application.

Never Destroy HttpClient Object With C# Using Statement:

One of the most common mistakes or bad way of implementing HttpClient is destroying it by using C# Using statement. The reason behind this bad practice is the HttpClient implement 'IDisposible' interface. Because of 'IDisposible' interface, every developer believed it is good to destroy the HttpClient object to free up the resource but it is an incorrect assumption. One of the main problem caused by HttpClient object destruction is orphan web sockets that leads Port Number issues.

Example of destroying HttpClient object with Using Statement:
Using(var httpClient = new HttpClient())
  // code sample

Let's understand what happens if we destroy the HttpClient object in upcoming steps. To understand let's assume we have .Net Core application hosted on a server, let's assume we have only 3 port numbers available on the hosting server to create WebSocket(note:- in real server port numbers will be in 1000's).
  1. Now in our application, let's assume we have implemented HttpClient to be destroyed once it's usage is finished.
  2. Now the first user requested our application, on receiving request application creates a new HttpClient object inside the c# Using Statement(which means HttpClient object destroyed once code executes out of Using statement)
  3. HttpClient object picks up a HttpRequestMessageHandler object from its pool.
  4. Now HttpRequestMessageHandler object picks '1' port number available in the pool of port number(we assumed total '3' port numbers in the pool).
  5. Now using port number and information in HttpRequestMessageHandler opens WebSocket to create a communication channel.
  6. WebSocket once creates will not be closed immediately once its job is done. Because sockets are costly resources so they will wait for some time to serve if any new request comes from the application. So that the existing socket will be effectively used for the subsequent requests. But domain should be the same for subsequent requests to serve by the existing socket if the domain different new Websocket will be created.
  7. Now let's think our WebSocket created communication channel, then receiving output it will return a response to the application code.
  8. Now we got our response once our code execution comes out of C# Using statement, it will call the IDisposible interface which will destroy the HttpClient object.
  9. Destroying the HttpClient object means it will also break the communication with the WebSocket and HttpRequestMessageHandler. Now Websocket lost its communication with HttpRequestMessage, but WebSocket still alive as Orphan Websocket this means port number still be used by this Orphan Websocket and this Orphan WebSocket can't be used by any application. So here we can observe Server resources like the port number in a working mode without any purpose or we can say all those resources in useless mode. This leads to resource unavailability for subsequent requests to our application.
  10. Similarly, let's assume that same time we got 2 more user requests, now the same process we discussed in the above steps will execute for these 2 requests. So now we have 3 requests from the user to our application means our application creates 3 WebSockets to build a communication channel. This means all these WebSocket will be  Orphan WebSockets. So from this, we can understand we are out resource to create new WebSocket because now we don't have another port number to create 4th WebSocket.
  11. Now let's assume we got 4th user request now our application will search for the port number to create a WebSocket, but there no port numbers available at currently for the application because all ports are in use, so application waits for some time for the port number, finally it will throw an error like 'WebSockets Exhausted'(example exception), 'time out exception' etc.
  12. This is the main reason we need to avoid the destroying of the HttpClient object.

Solution Provided By HttpClientFactory:

HttpClienFactory will create a static instance of a HttpClient per Domain of the third-party API. So HttpRequestMessageHandler object will be lives a long time by connecting with WebSocket by setting the expiration time. By default expiration, time will 2 minutes for HttpRequestMessageHandler but we can increase that value based on our application requirements. Using this approach we can avoid orphan WebSocket and consumes fewer resources on the server.

Let's understand the steps of HttpClientFactory flow as follows:
  1. Let's assume User Requested (R1) to our application.
  2. Then in HttpClientFactory create a static instance of HttpClient. The static instance is for single time creation. HttpClientFactory creates a static instance per domain of third party API. All the requests for specific third party API will be handled by that HttpClient instance.
  3. Then HttpClient instance looks for the HttpRequestMessageHandler(HRMH1) object in the HttpRequestMessageHandler pool.
  4. Now HttpRequestMessageHandler(HRMH1) object contains all information to make API calls like Url, Payload, Token, Header's, etc.
  5. HttpRequestMessageHandler(HRMH1) object looks for the port number on the server. Then creates a WebSocket(WS1) that establishes a communication channel.
  6. Now let's assume another User Requested(R2) to our application. If (R1) and (R2) aim the same external API then HttpClientFactory provides the HttpClient instance which is created in previous steps. If (R1) and (R2) are requested for different third party API then the HttpClientFactory Provides the new static HttpClient instance. 
  7. So in our case let's assume both (R1) and (R2) user requests want the same external API. Now HttpClient instance looks HttpRequestMessageHandler object. For (R1) we know the (HRMH1) object is used. So now HttpClient checks if (HRMH1) is free to serve (R2). If (HRMH1) is free and it has a connection with active WebSocket(WS1) to serve (R2). Here we can observe (WS1) serve both (R1) and (R2) instead of creating new WebSocket(WS2). So in this process, we are efficiently utilizing our server resource. Let's check another case also like (HRMH1) is busy serving (R1) request which means (R1) request still in progress, then HttpClient instance picks up another HttpRequestMessageHander(HRMH2) object. Then (HRMH2) picks up a new port number on the server and creates a new WebSocket(WS2).
  8. The similar way all the user requests will be effectively controlled by the HttpClientFactory.

Wrapping Up:

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

Follow Me:


Popular posts from this blog

Endpoint Routing In Asp.Net Core

How Routing Works In  Core 2.1 And Below Versions?: In Asp.Net Core routing is configured using app.UseRouter() or app.UseMvc() middleware. app.UseMvc(routes => { routes.MapRoute( name: "default", template: "{controller=Home}/{action=Index}/{id?}"); }); Here in Dotnet Core version 2.1 or below versions on the execution of route middleware request will be navigated appropriate controller matched to the route.

An operation or functionality which is dependent on route URL or route values and that need to be implemented before the execution of route middleware can be done by accessing the route path from the current request context as below
app.Use(async (context, next) => { if(context.Request.Path.Value.IndexOf("oldvehicle") != -1) { context.Response.Redirect("vehicle"); } else { await next(); } }); app.UseMvc(routes => { routes.MapRoute( name: "vehicleRoute", template: "vehicle", defaults:new { …

GraphQL API Integration In Asp.Net Core Application

GraphQL is a query language for your API and a server-side runtime for executing queries by using a type system you define for your data. GraphQL can be integrated into any framework like ASP.NET, Java, NestJs, etc and it isn't tied to any specific database or storage engine and is instead backed by your existing code and data.
How GraphQL API Different From Rest API: GraphQL exposes a single end-point or route for the entire application, regardless of its responses or actions.HTTP-POST is the only Http verb recommended by the GraphQL.The client applications (consumers of API) can give instructions to GraphQL API about what type of properties to be returned in the response. Building Blocks Of GraphQL API:The main building blocks of GraphQL API is Schemas and Types. A 'Schema' in GrpahQL API describes the functionality available to the clients connect to API. Schema mostly consists of GraphQL Object Types, Queries, Mutations, etc.Types likely to be called Grap…

ASP.NET Core Web API Versioning

Introduction: An iteration and evolutionary changes of an ASP.NET Core Web API is handled by Versioning. Versioning of an API gives confidence to the clients which consumes API for a long time. Any changes or development of an API will be accessible using the new version and it won't cause issues to the clients consuming the old version of API.
When To Use Versioning:Any API response changes.Developing an API by implementing testing levels like 'Alpha', 'Beta', and 'RC' versions before releasing Production.Deprecating an API which means API going to be removed or upgraded by a version within a short period. Versioning Types:Query String VersioningUrl Path VersioningMedia Type Versioning API Version Nuget: To Configure versioning to AspNet Core Web API Microsoft provided a library(Microsoft.AspNetCore.Mvc.Versioning). So to use the versioning library please install NuGet below.
 Install-Package Microsoft.AspNetCore.Mvc.Versioning -version 4.0.0 Register API V…

.NET Core MVC Application File Upload To Physical Location With Buffered Technique

Buffering Technique In File Upload:The server will use its Memory(RAM) or Disk Storage to save the files on receiving a file upload request from the client. Usage of Memory(RAM) or Disk depends on the number of file requests and the size of the file. Any single buffered file exceeding 64KB is moved from Memory to a temp file on disk. If an application receives heavy traffic of uploading files there might be a chance of out of Disk or RAM memory which leads to crash application. So this Buffer technique used for small files uploading. In the following article, we create a sample for the file uploading using .NET Core MVC application.
Create The .NET Core MVC Project: Let's create a .NET Core MVC project, here for this sample I'm using Visual Studio Code as below.  Check the link to use the Visual Studio Code for .NET Core Application.
IFormFile: Microsoft.AspNetCore.Http.IFormFile used for file upload with buffered technique. On uploading files from the client, then the entire …

Ionic Picker Sample Code In Angular

Introduction: Ionic Picker(ion-picker) is a popup slides up from the bottom of the device screen, which contains rows with selectable column separated items.
The main building block of ion-picker as follows: PickerControllerPickerOptions PickerController: PickerController object helps in creating an ion-picker overlay. create(opts?: Opts): Promise<Overlay> PickerController create method helps in create the picker overlay with the picker options
PickerOptions: PickerOptions is a configuration object used by PickerController to display ion-picker.
Single Column Ionic Picker: single.item.picker.ts: import { Component } from "@angular/core"; import { PickerController } from "@ionic/angular"; import { PickerOptions } from "@ionic/core"; @Component({ selector: "single-column-picker", templateUrl:"single.item.picker.html" }) export class SingleItemPicker { animals: string[] = ["Tiger", "Lion", "Elephant"…

Blazor WebAssembly Dynamic Form Validation

Introduction: In Blazor WebAssembly(client-side framework) form validation can be done with Data Annotations. Using Data Annotations we can validate form either by default validation attributes or by creating custom validation attributes. Using this Data Annotation attribute we can dynamically add or remove validation on a specific field in a form.
Create Blazor WebAssembly Project: To create a Blazor WebAssembly template project need to install the latest version of VisualStudio 2019 for rich intelligence support or we can use VisualStudio code but less intelligence support from the editor. Click here to know about Blazor WebAssembly template creation. Blazor WebAssembly is in preview mode, not yet ready for production.
Create Razor Component: After creating a sample project using the Blazor WebAssembly template, in "Pages" folder add new Razor Component, name it as "UserForm.razor"
Add Route: In Blazor routing can be configured using @page  directive, and URL should b…

Asp.Net Core MVC Form Validation Techniques

Introduction: Form validations in any applications are like assures that a valid data is storing on servers. All programing frameworks have their own individual implementations for form validations. In Dotnet Core MVC application server-side validations carried on by the models with the help of Data Annotations and the client-side validations carried by the plugin jQuery Unobtrusive Validation. jQuery Unobtrusive Validation is a custom library developed by Microsoft based on the popular library jQuery Validate.
In this article, we are going to learn how the model validation and client-side validation works in Asp.Net Core MVC Application with sample examples.
Getting Started: Let's create an Asp.Net Core MVC application project using preferred editors like Microsoft Visual Studio or Microsoft Visual Studio Code. Here I'm using Visual Studio.
Let's create an MVC controller and name it as 'PersonController.cs' and add an action method as below.
PersonController.cs: us…

Blazor Server CRUD Operations

Introduction: Blazor Server is a web framework to develop server-side single-page applications. Blazor is made up of components with the combinations on C#, Html, CSS.  Blazor Server is production-ready from the .Net Core 3.0.  Blazor Server Working Mechanism:Blazor Server is a very light-weight web development framework. In Blazor Server, not all code gets downloaded to the client browsers. Blazor Server made of components these components can be a block of code or page with respective navigation. Blazor server application communicates with the server with a SignalR background connection which is inbuilt functionality. Application click,  form submission, change events, application page navigation every operation is carried out by the SignalR connection by communicating with the server. Blazor updates the Html DOM very gently on every data update without any overhead. Blazor Server application maintains a nice intelligent tree structure to update the required information or changed …

NestJS API CRUD Operations With MongoDB

Introduction: NestJS is a framework used to develop server-side applications. NestJS built on top of Node.js frameworks like Express. It is a combination of Progressive Javascript, Object-Oriented Programming, Functional Programming, and Functional Reactive Programming.
Nest CLI Installation: Using Nest CLI we are able to generate the NestJS starter project with the default template. To install Nest CLI globally over our system open command prompt and run the command
npm i -g @nestjs/cli Now create a sample project by using Nest CLI command  nest new your_project_name package.json: Now open the package.json file from the sample application created, you can observe few properties like "scripts", "dependencies", and "devDependencies".
"dependencies" contains all plugins to be installed and used them to run the application.
"devDependencies" contain all plugins to be installed and used them at the time of application development.

How Response Caching Works In Asp.Net Core

What Is Response Caching?: Response Caching means storing of response output and using stored response until it's under it's the expiration time. Response Caching approach cuts down some requests to the server and also reduces some workload on the server. Response Caching Headers: Response Caching carried out by the few Http based headers information between client and server.
Main Response Caching Headers are like below
Cache-ControlPragmaVary Cache-Control Header: Cache-Control header is the main header type for the response caching. Cache-Control will be decorated with the following directives. public - this directive indicates any cache may store the response.private - this directive allows to store response with respect to a single user and can't be stored with shared cache stores.max-age - this directive represents a time to hold a response in the - this directive represents no storing of response and always fetch the fresh response from serverno-store…