Legacy systems often rely upon a combination of proprietary data models, proprietary data formats, and proprietary transport protocols. For this reason the Legacy Wrapper pattern is often used…

Question

Options

• AAtomic Service Transaction
• BService Messaging
• CService Broker
• DMessaging Metadata

• A
  2% (1)
• B
  4% (2)
• C
  92% (44)
• D
  2% (1)

Explanation

Service Broker (C) is correct because legacy systems expose proprietary formats and protocols that modern consumers cannot natively understand - a Service Broker sits in the middle, handling routing, protocol translation, and data format mediation between the wrapped legacy service and its callers. The Legacy Wrapper alone only hides the legacy internals behind a service facade; the Service Broker is what bridges the communication gap at the transport and data level.

Atomic Service Transaction (A) addresses transactional integrity across multiple services - a coordination concern, not a communication/format translation concern. Service Messaging (B) is a broad pattern for asynchronous inter-service communication and doesn't specifically solve proprietary protocol bridging. Messaging Metadata (D) involves decorating messages with headers or context - useful for tracing and routing hints, but not a solution for format or protocol incompatibility.

Memory tip: Think of the pair as a two-layer wrapper - the Legacy Wrapper wraps the system, and the Service Broker wraps the conversation. Proprietary = needs a broker to "broker the deal" between old and new.

No community discussion yet for this question.