Epseelon
Software for People
  • email
  • facebook
  • twitter
  • linkedin
  • Contact
  • My personal blog
  • Looking Forward
  • Blockchain Awareness
Select Page ...

Monthly: January, 2011

My Case for DTO's

Sebastien January 6, 2011 Export, Flex, Geek Culture, Groovy/Grails, Model-Driven Architecture, Rich Internet Applications, Tech Stuff 16 Comments

In many of my posts about Grails and Flex integration, I take for granted that I use Data Transfer Objects to transfer data between my Grails backend and my Flex frontend. Put simply, Data Transfer Object are pure data containing classes different from the domain entity classes used to store data in the backend. I take it for granted because I’m deeply convinced that it’s the best way to do things and so far, experience has never proved me wrong. But I often get this question in comments or by mail (this is for you Martijn): why bother create an entirely separate class structure and copy data from entities to DTO’s and back instead of just using entities?

Share this:

  • Print
  • Email
  • Facebook
  • Twitter
  • Google
  • LinkedIn
  • Reddit
    • Copyright © 2013 Epseelon sprl. All Rights Reserved
      loading Cancel
      Post was not sent - check your email addresses!
      Email check failed, please try again
      Sorry, your blog cannot share posts by email.