Communication System

Systems, subsystems, and services within the INTERSECT federated ecosystem need to be able to communicate with each other using standardized ommunication and programming interfaces. The Communication System (CS) provides the means for such communication using messages. It generally supports the sending and receiving of messages within the INTERSECT federated ecosystem without exposing this functionality as a service itself, as it is a built-in functionality of a client interacting with a service and its microservice(s). A service and its microservice(s) may be a client. The CS has the following built-in functionalities:

  • Point-to-point Messaging

    • Send: Send a message to a service (and its microservice)

    • Receive: Receive a message from a service (and its microservice)

  • Publish/Subscribe Messaging

    • Message Subscribtion: Subscribe to a certain class of messages

    • Message Publication: Publish a message

The CS has also the following services and microservice capabilities (mapping the System-of-Systems Architecture to the Microservices Architecture):

  • Federation Messaging Service

    • Message Routing Capability: Route messages between different participants in the federation of systems

The CS supports the Microservice Interaction Patterns.

Minimum requrement

At minimum, there must be one and only one CS in an INTERSECT federated ecosystem, as the CS spans over all infrastructure systems within the same INTERSECT federated ecosystem. Individual services of the CS may be distributed across infrastructure systems as needed, where some services may only exist once.

At minimum, the CS supports the Microservice Interaction Patterns.

Optional requrement

Optionally, multiple INTERSECT federated ecosystems may exist that operate either completely indepenently from each other or collaborate with each other, but each INTERSECT federated ecosystem has only one (its own) CS.