Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 1
    Why should a service not make another request? Commented Aug 31, 2019 at 7:19
  • 1
    @DocBrown Because it introduces a dependency both runtime and organizationally. Commented Aug 31, 2019 at 7:26
  • 1
    @RobertBräutigam: sure it does. But the question was, does such a dependency contradict the definition of SOA. I am not enough an expert on this to give an answer, but if the OP suspects it might contradict such a definition, he should tell us why he thinks so, ideally give some references. That's why I asked. Commented Aug 31, 2019 at 8:03
  • @RobertBräutigam: Dependencies are not evil. In fact, they're necessary, especially if the problem domain also has such a dependency intrinsically. Commented Aug 31, 2019 at 18:05
  • 1
    @RobertHarvey I don't follow your logic. Whether something is necessary or not has no bearing on what effect it has on your architecture. Dependencies always complicate things, because they are essentially an additional constraint you have to deal with. Even if they are necessary - and a lot of times they are just a result of bad design in my opinion - that still doesn't change any of that. Commented Aug 31, 2019 at 19:23