Which best describes a business outcome derived from implementing an ESB service gateway pattern?

Question

Options

• AReduced development costs from coding one service mediation
• BReduced development costs by leveraging IBM best practices.
• CImproved visibility into runtime operations.
• DImproved service life cycle management.

• A
  77% (33)
• B
  2% (1)
• C
  7% (3)
• D
  14% (6)

Explanation

The following specific gateway patterns have been identified: Security gateway This rather specific example of a gateway pattern offloads all "non-standard" security processing from the main infrastructure and will execute authentication, authorisation and possibly audit before calling the true destination. In this mode there is almost always a trusted link between the gateway and other parts of the ESB so that the security model required for those other parts of the ESB can be simplified. Security gateways may reside in a different security zone to the rest of the ESB and would provide connectivity to external clients. This pattern would support a wide range of incoming security protocols while simplifying security in other ESB Service connector The gateway pattern can provide the simplest possible way of connecting a number of existing services into an ESB when introduced as part of an enterprise architecture based on service oriented principles. The gateway introduces a point of control in the enterprise architecture and can bring a range of ad hoc services under the control of a service registry and associated governance but without the need to develop individual mediation flows for each service. Messages enter the gateway and are routed onwards to an end provider, to a provider facade or to a further mediation flow. Boundary mediator The boundary mediator pattern extends the service connection pattern by enabling standard mediations to be applied to all incoming (and/or outgoing) service requests or messages. These standard (content independent) mediations are developed once in the gateway and can be applied to all incoming messages. These mediations may include any or all of validation, logging, audit, authentication and authorisation. They may be applied universally or selectively based on the gateway properties, lookup based on request data or on data within the incoming request (normally in headers). Note 1: An ESB Gateway at a minimum provides service address translation between the ESB and the external consumers/providers. In practice the ESB Gateway will often provide additional services such as security, message transformation and Partner data management. Note 2: A gateway is a part of a message bus or service bus which provides boundary functions which apply to all incoming messages and are not format dependent. Boundary functions typically utilise data from standard headers (at transport, SOAP or even data level) to determine what action to take but do not need to understand the complete format of the message data (or body). A gateway pattern may then call a service directly or invoke a further pattern.

No community discussion yet for this question.