Why are data transfer objects (DTOs) an anti-pattern?

java ejb dto anti-patterns data-transfer-objects
ntownsend picture ntownsend · Sep 17, 2009 · Viewed 57.4k times · Source

I've recently overheard people saying that data transfer objects (DTOs) are an anti-pattern.

Why? What are the alternatives?

Answer

KLE picture KLE · Sep 17, 2009

Some projects have all data twice. Once as domain objects, and once as data transfer objects.

This duplication has a huge cost, so the architecture needs to get a huge benefit from this separation to be worth it.

Related questions

Cannot instantiate the type List<Product>

I have the following code: List<Product> product = new List<Product>(); The error: Cannot instantiate the type List<Product> Product is an Entity in my EJB project. Why I'm getting this error?

Read More
Should I use @EJB or @Inject

I have found this question: What is the difference between @Inject and @EJB but I did not get any wiser. I have not done Java EE before nor do I have experience with dependency injection so I do not understand …

Read More
Stateless and Stateful Enterprise Java Beans

I am going through the Java EE 6 tutorial and I am trying to understand the difference between stateless and stateful session beans. If stateless session beans do not retain their state in between method calls, why is my program acting …

Read More