First off I hate these types of analogies as I feel they cloud the issue. You can really think of this as two different semantic domains: the solution domain a

First off I hate these types of analogies as I feel they cloud the issue. You can really think of this as two different semantic domains: the solution domain and the problem domain. You can break them down as (controllers, errors, storage, templates, validators) vs (posts, comments, users), respectively. His layout is pretty consistent with standard Java/Spring/Hibernate project structures. In my experience when you work on a project like this you are working on something in the problem domain like users and when you make a change you have to go hunt down each solution domain component in a separate package. It has always seemed to me that it is better to organize using the problem domain as it clusters functionality that you are likely to work on concurrently.