(May 30, 2016 at 12:14 pm)Marsellus Wallace Wrote: in a big project, the MVC approach is the way to go, it even makes teamwork easier to achieve cuz it got it split in a very good way.
At my job we've taken a different approach. We use mostly Spring REST / Hibernate on the back end, GWT for web clients. That scheme allows us to allow b business partners to produce their own front-end if they don't want to use ours. Our use cases are different than a typical web application, however.
We can split out the work at three or four different layers quite easily. I work on the REST API mostly, and most of the time I have no idea what the UI guys are up to, nor do I particularly care.
In practice it is very similar to MVC though we have made very little use of the actual Spring MVC API. B the here's always more than one way to accomplish the same goals.
