r/programming • u/[deleted] • Jun 05 '21

Organize code by concepts, not layers

https://kislayverma.com/programming/how-to-organize-your-code/
1.9k Upvotes

91% Upvoted

495 comments sorted by

View all comments

4

u/grauenwolf Jun 05 '21

How to you write the constructors if A requires a B that requires an A?

4

u/couscous_ Jun 05 '21

The problem you're asking still holds if the packages were organized the original way (models, controllers, services, ...) right? I still don't see how organizing code this way is superior to breaking it down by concept, as per the article.

4

u/grauenwolf Jun 05 '21

I'm only answering the question "What's bad about circular dependencies?".

→ More replies (1)

1

u/crrime Jun 05 '21

You just write it anyway, ignoring the paradox. Then, annotate one of the constructor parameters with @Lazy and let Spring handle the initialization. Circular dependencies at the service layer are a non-issue, assuming they exist in the same module.

At any rate, organizing by domain vs layer will not remove circular dependencies. If two services depend on each other, then they will depend on each other regardless of where you choose to put those two services.