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.
Referinte: http://www.objectmentor.com/resources/articles/srp.pdf

Comments

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

    ReplyDelete

Post a Comment

Popular posts from this blog

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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…