I am trying to understand various design patterns when Mediator is added to an existing IS based service landscape.
- Is communication between Mediator and IS service always HTTP? This will contribute to overall latency of the virtual service.
- Consumer -> Enterprise web service -> provider. In this scenario, where to put virtual service?
2.a Consumer -> VS -> Enterprise web service (IS) -> VS -> Provider web service.
I think above setup is required for protocol and security bridging between consumer and provider.
- Consumer -> VS -> Provider
Above pattern uses IS for request and response transformation. Incoming and outgoing policies can be enforced in Mediator. No need of inbound and outbound virtual services.
Can the same provider service be exposed over HTTP and JMS? In this case, I am assuming 2 virtual services to be created one for HTTP and one for JMS.
Can VS route to another VS? What will be mode of communication here? HTTP or some sort of native protocol?
Where can I get more details in these topics?