Biggest sin that causes many of the problems that this framework is trying to solve is passing an Entity object as a return on a REST call. This is hugely wrong. Entity objects should not pollute the domain of the application. The objects should be copied out to other objects which represents the model of the external API. This is littered through most Spring examples though.
I have been using vaadin since 1 year and i can say that it's the best ui framework from the technical debt point of view
Do you use Flow or Hilla?
Very good presentation and an excellent solution to build moderate scale applications rapidly.
This is a great presentation 👍.
How well it can integrate with React JS?
Biggest sin that causes many of the problems that this framework is trying to solve is passing an Entity object as a return on a REST call. This is hugely wrong. Entity objects should not pollute the domain of the application. The objects should be copied out to other objects which represents the model of the external API. This is littered through most Spring examples though.
That is not the problem of framework. You need to take some time from your busy schedule to refractor your code. DDD is not framework dependent.
You can just map entity to dto and return dto. That simple
@@orhn Infrastructure entities should not be passed to the service layer.
@@KangoV Agreed
DDD, ubiquitous language, Service, Value Type, Entity, 1455 useless classes.