Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There may not be one solution/off-the-shelf component that might help you. </p> <p><strong>Problem 1:</strong><br> The basic problem can be solved via an ESB, as it provides <em>location transparency</em> and <em>service aggregation</em>. A regular ESB <strong>mediates/brokers</strong> requests between service consumer and service provider.<br> Take a simple example:</p> <blockquote><pre>Service_A depends on Service_B Service_C depends on Service_B Service_B depends on Service_D </pre></blockquote> <p>In this scenario, the best way to progress is this: </p> <ol> <li>Define contracts exposed by <code>Service_B</code> and <code>Service_D</code> as <em>external dependencies</em> (possibly as a web service, though an ESB supports multiple protocols) in services <code>Service_A</code>, <code>Service_C</code> and <code>Service_B</code>, and consume via an ESB. </li> <li>In ESB, to start with, route thes services <code>Service_B</code> and <code>Service_D</code> on the same instance. </li> <li>If you migrate <code>Service_D</code> and <code>Service_B</code> as <code>Service_Dx</code> and <code>Service_Bx</code> on a different location, the ESB can be reconfigured to route to the new location. Also, an ESB can be configured to route to <code>Service_B</code> or <code>Service_Bx</code> based on some set of parameters (eg., test data to <code>Service_B</code> and production data to <code>Service_Bx</code>)</li> </ol> <p><strong>Problem 2:</strong><br> The problem of IOC could probably be hard to achieve; there may not be a need.<br> I presume the clients, instead of consuming from a known location, are injected with the whereabouts of service location. This in reality transfers the configuration to client side. With this, for every new client added to the system there needs to be a separate configuration control. This might lead to logistical issues.</p> <p><em>Please post your final solution, very interested to know your approach.</em></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload