Skip to main content

Short brief - Request-Response, Asynchron and Fire and Forget patterns

Un apel spre un serviciu poate sa fie facut in diferite moduri. Cele mai uzuale moduri sunt cele care respecta paternul Request-Response si Asynchron. Pe langa aceste doua paternuri mai exista inca unul, dar care este mai rar folosit Fire and Forget.
Request-Response pattern- se refera la faptul ca pentru fiecare request facut se asteapta raspunsul.
Response response = service.CallService(request)
Asynchron pattern - este un patern bazat pe evenimente. Odata ce un apel a fost facut, aplicatia nu asteapta raspunsul de la server. Cel care face apelul trebuie sa se inregistreze la un eveniment care o sa fie declansat cand raspunsul soseste.
service.ResponseEvent += new EventHandler(ResponseReceived);
service.CallServiceAsync(request);
Fire and Forget pattern - este destul de asemanator cu paternul Asynchron, doar ca odata comanda trimisa nu ne mai intereseaza ce se intampla cu aceasta.
service.CalService(request);    // Metoda nu returneaza nimica
Exista diferite scenarii cand Fire and Forget este recomandat sa fie folosit. Conditia principala care trebuie sa fie implinita ca sa putem folostii acest patern este ca sa ne putem asigura ca request-ul ajunge la server - avem un protocol ce ne garanteaza ca mesajele au ajuns la destinatie( de exemplu daca folosim cozi de mesaje care ne asigura ca mesajele nu se pierd - de exemplul MQ).
In cazul in care avem servicii cu un volum mare de request-uri, atunci poate pentru unele tipuri de request-uri putem sa folosim acest patern. De exemplu pentru cele in care rezultatul este format din mesaje precum Okay.
Cele mai mari dezavantaje apar in momentul in care ceva nu functioneaza bine. Debug-ul este destul de complicat si de obicei necesita interventia umana pentru a putea gasi problema. Problemele care pot sa apara sunt la nivelului protocolului care ar trebui sa ne garanteze ca mesajele ajung la destinatie.
Un alt mod de a apela un serviciu este de a face unu sau mai multe request-uri de tipul Fire and Forget, iar apoi la un moment dat sa se verifice daca a venit un raspuns( intr-un cache, in baza de date etc) - in cazul in care raspunsul se pune intr-o locatie unde atat clientul cat si serverul le pot accesa
Nu trebuie confundat un apel de forma:
service.CallService(request,()=>{ ... });
ca si cum ar fi un apel de tip Fire and Forget. Orice metoda sau lambda expresion specificata ca si al doilea parametru care este apelata in momentul in care raspunsul soseste de la server reprezinta un apel de tip asincron.

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…