design patterns - Why should I isolate my domain entities from my presentation layer? -


A part of a domain-based design that does not contain much detail, is that how you and your interface Domain model should be separated I am trying to convince my colleagues that this is a good practice, but I do not seem to have much progress ...

They use domain entities, Where they make fun in the presentation and interface layers anytime. When I argue them that they should use the display model or DTO to separate the domain layer from the interface level, they respond to the counter that they do not see the value of the business in doing something like that, because now You have a UI object to maintain as well as the original domain object

so I'm looking for some concrete reasons with which I can use it The front. Specifically:

  1. Why should not we use the domain object in our presentation layer?
    (If the answer is clear, 'decoding', then please explain why this is important in this context)
  2. Do we use additional objects or constructions to separate our domain objects from the interface should do?

Very simple, the reason for implementation and flow is yes, your presentation layer is used for your business items Need to know about them so that they can be displayed properly. Yes, initially it seems that there is a lot of overlap between the two types of objects. The problem is that as time passes, things on both sides are added, changes in presentation, and presentation level needs include those things. Are developed to do that are completely free from your business layer (color, for example). In the meantime, your domain objects change over time, and if you do not have proper decugging from your interface, then you can risk the risk of spoiling your interface layer by appropriately benign changes in your business object.

Personally, I believe the best way to approach things is through a strictly implemented interface pattern; That is, your business object layer exposes an interface which is the only way it can be transmitted; No implementation details (i.e. domain objects) about the interface are not revealed. Yes, this means that you have to implement your domain object in two places; In your interface layer and your bow layer but it can help improve decoding while improving it, while starting it may seem like extra work, decoupling will save tons of work at some point in the future.


Comments

Post a Comment

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

I'm having trouble overriding a ModelForm save method. I get this error I'm: Exception type: TypeErier Exception Value: Save () found an unexpected keyword argument 'committed' My intentions include a form 3 fields Submit several values ​​for, then create an object for each combination of those areas, and to save each object file models.py class collarsult type (models.Model): id = model. AutoField (db_column = 'icontact_result_code_type_id', primary_key = true) callResult = models.ForeignKey ( 'CallResult', db_column = 'icontact_result_code_id') campaign = models.ForeignKey ( 'campaign', db_column = 'icampaign_id') CALLTYPE = models.ForeignKey ( 'CALLTYPE', db_column = 'icall_type_id') agent = models.BooleanField (db_column = 'bagent', default = true) teamLeader = models.BooleanField (db_column = 'bTeamLeader', default = true) active = models.BooleanField (db_column = Django.form...
Read more

html - CSS autoheight, but fit content to height of div -

I have a div in which there are three children- div in the left and middle div: float: left while true: float: true because it is my layout Actually will spoil, I've used ClearFix Hack: .cf {zoom: 1; }. Cf: First,. Cf: {content: ""; Display: Table; }. Cf: After {clear: both; } It still works, but I want to be the right div an indicator. So it should fill 100% of the parent unit of height. How can I complete this? PS is the full code: & Lt; / Div & gt; & Lt; Div class = "mobile_content" & gt; & Lt; H5 & gt; {{Data.titel}} & lt; / H5> & Lt; Table & gt; & Lt; TR & gt; & Lt; Th & gt; Komponist: & lt; / Th & gt; & Lt; TD & gt; {{Data.komponist}} & lt; / TD & gt; & Lt; / TR & gt; & Lt; TR & gt; & Lt; Th & gt; Instrument: & lt; / Th & gt; & Lt; TD & gt; {{Data.instrumente}} & lt; / TD & gt; & Lt; / TR & gt;...
Read more

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -

I have been trying to use Qt5 multimedia to record audio with QAudioInput, however, when I see If QAudioInput is started, it increases the master volume of my sound device to 100%. How can I prevent QAudioInput from changing the master volume? My current development platform is Linux with PalsAdio (with flat audio disabled). How can I use QAudioInput : QAudioDeviceInfo device_info = QAudioDeviceInfo :: defaultInputDevice (); QAudio format format; Format.setSampleRate (44100); Format.setChannelCount (1); Format.setSampleSize (16); Format.setCodec ("Audio / PCM"); Format.setSampleType (QAudioFormat :: SignedInt); Format.setByteOrder (QAudioFormat :: LittleEndian); Std :: cout & lt; & Lt; Device_info.deviceName (). ToUtf8 (). ConstData () & lt; & Lt; Std :: endl; QAudioInput * default_device = new QAudioInput (device_info, format); QIODevice * default_io_device = default_device-> Start (); a QAudioInput.setVolume () method is not you I ...
Read more