Deck Plan integrations

Integrations with optional Services

Here the integrations will be modeled into separate services, one per microservice depended. The key behind this approach is that this integration service will be deployed only if the service on which we depend has been so. This strategy works for services of different applications, because not all applications are deployed at every installation, therefore the integration should not exist at all in those cases. Some examples of this situations are, integrations for ServiceOrders from AIMS application or Inspections from iInspector application.

Integrations with required Services

This kind of integrations will live inside of the bounded context of the microservice that needs the integration. An example of this type is the integration between Locations and GeneralArrangements. Locations is common to most of the applications and is required by General Arrangements in order to maintain consistent data, since its the source of truth for the Locations displayed in the map.