CODEWITHSUNDEEP
javadesign-patternsdata-transfer-objects
user3707778
user3707778

Reputation: 47

Design pattern for DTO

I have a web application using jdbc for database calls. I have a service, dto and dao layer. I have a request xml which is huge. Can I pass the request object to dao method or should I transfer the request to a dto model and then pass the dto object as a paramter to my dao method? Which is the right approach??

public TestServiceClass addSurveySubmitDetails(TestRequestXML testRequestXML){
          //call to dao method
          TestDao = testdao = new TestDao(testRequestXML);

   }

         OR

    public TestServiceClass addSurveySubmitDetails(TestRequestXML testRequestXML){

         //create dto object
         TestDTO testDTO = new TestDTO();
         testDTO .setId(testRequestXML);

          //call to dao method
          TestDao = testdao = new TestDao(testDTO );

   }

Which is the right approach??

Upvotes: 0

Views: 2557

Answers (4)

MiguelMunoz
MiguelMunoz

Reputation: 4934

DTOs are really intended for remote calls. If you're sending data over the network to a different virtual machine, use a DTO. If you're sending data to another local class on the same virtual machine, don't bother with a DTO. A DTO is just an efficient way to transfer data remotely. It doesn't really have any advantages anywhere else.

Upvotes: 0

brewerof
brewerof

Reputation: 102

YAGNI is good idea, keep it simple design, where possible

Upvotes: 0

hgulyan
hgulyan

Reputation: 8239

It depends on your architecture, but as DTO is Data Transfer Object there's no reason to use them between service and dao layers.

You can have one for service layer I suppose like in code sample below, but anyway it depends on your application's architecture.

   public TestServiceClass addSurveySubmitDetails(TestDTO testDTO){
          TestRequestXML testRequestXML = testDTO.getId();
          TestDao = testdao = new TestDao(testRequestXML);

   }

More on DTO's

Data Transfer Object

LocalDTO

Upvotes: 2

Pacane
Pacane

Reputation: 21481

I don't think there is a right or wrong answer. It's pretty subjective in my opinion.

But I personally like to have a thin layer between the controllers and the services (assuming you're using the MVC pattern), that its only task is to convert requests (XML, Json, etc) to domain objects.

It is quite useful when you have complex domain objects or aggregates of which you need to show information in a view.

Upvotes: 2

Related Questions