Skip to main content

Enterprise Service Wrapper

Context​

There are different microservice-based projects within the company. Common functionality is designed as standalone microservices that shall be reused between these projects.

Problem​

  • The rest of the enterprise might use different integration, like communication protocols or data formats

Solution​

Introduce Enterprise Service Wrappers to encapsulate single microservices or the whole microservice-based system to facilitate integration over the existing integration technology, e.g., and ESB in case of SOA.

This technique represents the proxy microservice technique integrating in the opposite direction - not an external component into the microservice-based system, but integrating a microservice into the broader application landscape.

Maturity​

More data is required (only 1 source).

Sources of Evidence​

L46:

  • Enterprise Service Wrapper
    • component enables translation of older services between relevant protocols and data formats
    • = key component unlocking core business capability through microservices
  • 2-speed approach to services (mix with older SOA)
    • if there is mature SOA infrastructure, continue using it; but use microservice protocols (REST) for new APIs
    • if enterprise new to service management, employ the API management framework and protocols provided in the paper for new services and to proxy all services