"ddd" is a way of working, not a package

[JensRantil]

trafficstars

Just skimmed the source code. I think https://github.com/tlandeka/authentication-microservice-with-domain-driven-design/tree/main/src/main/java/com/tomo/mcauthentication/ddd package probably should be named domains - much more clear as DDD really just is a way of working.

[tlandeka]

Thanks for the comment. "ddd" should be extracted to a common library (according to this example and this one) What do you think? I followed the examples from the books. But let's say, my idea is to use the "boilerplate" (ddd) code on other projects and not broke the DRY principle, I would rather extract that piece of code to be reusable. Agree with you that DDD is a way of working.

[JensRantil]

Sounds like a good idea.

[tlandeka]

Removed ddd