Responses in-line, extra text removed.
On 3/20/2016 12:22 PM, Iury wrote:
> First of all, I would like to thank you for spent time helping me for
> fighting in favor of Java Community.
Thanks for the kind words. Like everyone else I am trying to do what I can.
> As I am developing a SPA ( AngularJs, JWT Token) and Rest Api Design
> (JavaEE 7) I would love to pick the first option however, as some
> legacy tables has more than 300k registers, I think I will sacrifice
> DDD a little 😄.
Everything that I said about the view layer applies to JavaScript Rich
Clients. In fact you will see that we use them in our application as
well. That said, applying DDD to a system that was not designed with DDD
in mind is a challenging task indeed. The second choice is certainly
valid if performance is an obvious concern. In my case it had always
been possible to do some pre-filtering of the data at the repository
layer via query parameters to avoid memory issues during
pagination/sort/filter (e.g. by executing an initial search or using
navigational breadcrumbs). That's obviously not always possible.
> How could I help you to contribute with Cargo Tracker JavaEE version
> in order to help support a lot of DDD beginners?
It's really up to you. We are always looking for ways to improve the
application. You could start by looking at the JIRA and picking up
anything that interests you:
https://java.net/jira/browse/CARGOTRACKER.
You can of course ask questions here if needed or just interact through
JIRA. I think everyone in the project gets the JIRA notifications.