This section outlines the various components and how they are deployed and interact with each other. These deployment levels keep the details to a minimum and highlights the various high-level components.
When deploying XMPro there are 3 options that can be utilized. The first being on-premises, the second being a hybrid where some components are on-premises and some are cloud based; and the last being completely cloud based.
The deployments have 3 (4 if you include the workflow product) website (IIS) requirements as well as 3 (4) databases backing those websites. Communication is via TCP/IP and MQTT/SOAP between the various components.
Hybrid
The difference here is that the Data Queues and CEP can be hosted on cloud infrastructure and called from within the rest of the components. The implication is that anything that is moved to the cloud vs on-premises needs to be able to communicate back to the on-premises components.
A drawback to take note of is latency between moving data from on-premises and cloud components and back, will play a part in deciding which components to move to the cloud vs leaving on-premises.