Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Nov 22, 2017
What is the package structure of your project? Most team have hard time explaining WHY their packages look the way they do. Even less can find any sense in their final layout. Do you know why package-scope is the default in Java? Do you know why most developers pretty much never use it? Do you have an architecture, with which you can easily and fast unit test 90% of your system, and not have to change your tests even after major refactoring? All Java devs understand class level encapsulation, some get microservices and modularity on a macro level ( few klocs). Not too many know how to design their code/architecture on a medium level. How to build easy to use building blocks. And so, most projects drift into kind of spaghetti mess. Let's see how we can make our situation a little bit better, using Domain Driven Design, package-private scope, sensible packaging structure, CQRS on microservices, and finally: hexagonal architecture. Because it is actually easier, than not doing it.