Add a comment


Re: Layers, hexagons, features and components

Of course the name of the repository will depend on the (domain) context, but we can imagine a "OurCustomers" type for instance.

Regarding the adapters, I tend to (YAGNI ;-) start with one single assembly for the whole Infrastructure part (with all the adapters). I may split it afterwards if necessary (i.e. due to real deployment or release management constraint). I stopped for years to create tons of projects/assemblies just in case I'd like to release & patch them separately (one day...)

"Why don't people mention this?" : because almost no one is using the Hexagonal Architecture pattern nowadays (unfortunately ;-( Having a widely known architect like you promoting this kind of simple design may probably change that brutal fact ;-)

Re: Layers, hexagons, features and components

HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
E-mail address
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).