Contents My experienceThe ecosystemThe fearsThe realityThe benefitsThe futureLet’s talk about it My experience As a software developer, I have been freelancing since 2010. Before that I was an employee for... Contents My experienceThe ecosystemThe fearsThe Read more…
It’s been a while since I posted my last article here. But tonight I just can’t help it. For a few weeks I’ve been reading MongoDB in Action, from Manning,...It’s been a while since I Read more…
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?
0 Comments