All geek questions in one place

Construction of an object at the client or business level?

Something that I noticed when looking at several .NET suites for beginners is that building business objects is often handled at the client level. Then the business object is transferred to the business layer for manipulation, serialization into a database, etc. Should we not abstract this code to the business layer so that the client only needs to transfer the necessary data? Is there an advantage to having a business layer with CRUD abstractions that accept objects only as arguments?

+3
source share
2 answers

I agree with you that interacting with a business word should be as simple as possible, with complex types and other complexity hiding, or what's the point. At the point where the user interface and business objects are connected, there should be as little complexity 0 as possible.

, . , , < 3 , 3 . , , : , , , . , , , . , - , , , , . . . , , ., .

  • < > Microsoft . - . , . , - .
  • SDK: , - ++ -. , , .
+3

Service . , , . -.

+2

Source: https://habr.com/ru/post/1725977/

More articles:


All Articles