Skip to main content

Single Responsibility Principle

Toata lumea a auzit de acest principiu. Pe scurt fiecare obiect trebuie sa aibe o singura responsabilitate.
Problema apare la interpretare. Fiecare persoana poate sa inteleaga diferit cand ne referim la responsabilitate.
Din cate am vazut pana acuma exista doua moduri in care se poate implementa SRP:
- fiecare metoda publica expusa de catre o clasa reprezinta o responsabilitate unica;
- fiecare obiect ar trebui sa aibe o singura responsabilitate.
Daca ne folosim de prima varianta, ajungem sa avem sute de interfete si clase abstracte, fiecare cu o singura metoda. In cazul in care respectam a doua varianta apare problema la interpretare. Cum putem spune ca o clasa are o singura responsabilitate si doar una.
De exemplu daca avem o entitate la care vrem sa adaugam metoda ToXml() am putea spune ca este corect din punct de vederea a SRP. Dar mai tarziu poate am avea nevoie de metoda ToString(). Aceste doua metode violeaza SRP.
Din pacate aceasta discutie ar putea sa continue la nesfarsit. Trebuie gasita un echilibru.
Pentru exemplul dat mai sus putem sa adaugam o metoda To() care prin intermediul unui formater sa ne returneze obiectul in formatul pe care il dorim.


  1. Din pacate multi programatori nu au auzit de acest principiu.. Chestia cu o singura metoda publica per clasa e clar o exagerare - Robert Martin (cel care a formulat principiul sub acest nume) explica ca prin 'responsabilitate' intelege 'reason to change'.

    Multe exemple care le da sunt voit exagerate un pic pentru a accentua ideea - ceea ce merita retinut din SRP e necesitatea de a evita aparitia de "god classes" care fac totul pentru toata lumea.
    Doar cine a avut de lucrat cu astfel de clase de baza, care combinau totul de la UI, business logic pana la persistenta, cu sute de metode publice si zeci de mii de linii de cod intelege cu adevarat importanta principiului - problema nu e la clasele cu 2-3 metode ce tin de acelasi layer si acelasi domain concept..


Post a Comment

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 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)

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

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…