4 ms·

Well, from a systems standpoint, it means a given "problem" is isolated to a single service, and is therefore not impacting the other services or interrupting t

• marcosdumay 8y ago
  That's only true if any given problem is isolated on a single service, because while you are making intra-service problems much cheaper and faster to fix, you are also making inter-service problems almost impossible to fix.
  • jcadam 8y ago
    Good point. I've seen situations where nobody would take ownership of a bug and fix it - you just had teams pointing fingers at each other...
    • BerislavLopac 8y ago
      This is precisely a symptom of unclear ownership responsibilities.
      • AnimalMuppet 8y ago
        No, it can be an issue of it being unclear in which component the bug actually is.
        • BerislavLopac 8y ago
          Which is a clear sign that your components are not sufficiently separate.
          • AnimalMuppet 8y ago
            Um, no. The real world is not that simple. It would be nice if it were. Or perhaps your statement is correct, but in the real world components are never sufficiently separate. So, while your statement may be correct by definition, it is not useful.
            • james_s_tayler 8y ago
              I think you really nailed it with this one. I can imagine there being a normal distribution of 'separateness' of software and the rare top tail-end of the distribution gets it perfectly right, most are in the middle somewhere between 'service oriented architecture' and 'ball of mud' and some are just at plain ball of mud.
            • BerislavLopac 8y ago
              You are misreading my words.
              • AnimalMuppet 8y ago
                Perhaps so. Would you care to explain? Your statement here doesn't give me much to go on.
                • BerislavLopac 8y ago
                  Well I meant it quite literally: if it is not clear which component has the bug, the components are not separate enough. You also say: > in the real world components are never sufficiently separate But the separation of components is not an issue of "real world", it is a function of design and implementation. It is absolutely to the developers how independently the components will be implemented; if there is no way to test them in isolation, then they are not really separate components. Take this website, and your browser, as an example. They are obviously connected, as you're using the latter to access the former, but they are completely independent: you can access other pages with the browser, and you can use other methods (other browsers, or curl, or Postman etc) to access this page. Each can be tested separately, and even when they are used in conjunction they don't directly depend on each other, but rather on a set of standards (HTTP, HTML, CSS etc) understood by both.