Ask questions and see you at November, 2nd, 8.PM. CET: https://vimeo.com/event/154379
Also checkout recent episode:
Please keep the questions Jakarta EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions.
Upcoming airhacks.tv events are also going to be announced at meetup.com/airhacks
Hey Adam,
you recently said something like "some people believe that using DTOs is the right way" and I would like to know why you hate DTOs so much 😆
I work on commercial applications that have entity models which cover multiplie use cases, not just CRUD. Depending on the use case, I need different parts of an entity, but never all information, so I use DTOs to reduce the amount of data that is fetched and exposed. What kind of magic would you use to approach something like that without DTOs?
I am the author of Blaze-Persistence Entity-Views which aims to reduce the necessary boilerplate to implement an efficient DTO approach. You define DTOs as annotated interfaces and can apply this projection onto a query i.e. a query is transformed to produce the DTO type efficiently. This works on top of JPA.
If your sole concern with DTOs is the boilerplate, what do you think about such an approach?