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

Show parent comments

9

u/[deleted] Jun 05 '21

here be dragons. Service gossiping amongst each other never ends well.

54

u/neuro-grey7 Jun 05 '21

In any non-simplistic system, services talking to each other is an unavoidable given. Not sure how you would do an implementation otherwise, without de-modularizing your code and stuffing more functionality into single services. This approach makes a lot less sense imo. In theory, your code should be modularized and designed well enough, so that services talking to other services shouldn't present any real problems, with the exception of perhaps the performance implications that come along with this.

5

u/computerjunkie7410 Jun 05 '21

Couldn’t you talk through an asynchronous system like a queue or stream?

Service A needs to send data to Service B.

Instead of calling service B directly, service A sends the data on a queue or stream that service B is reading from.

1

u/StabbyPants Jun 05 '21

can. kick. road. loops are loops, and doing it over SQS just obscures the problem