Single Host, Single Pod Deployment

This section explains the architecture and deployment of a single host and single pod topology.

Advantages of the single host single pod deployment topology are:

  • Requires minimum steps to start TIBCO PSI
  • Requires minimal hardware
  • Easy to install
  • Keeps multiple versions of TIBCO PSI ready, but starts only the one which is required
  • No interference among different versions of TIBCO PSI as they have individual environment settings

Limitations of the single host single pod deployment topology are:

  • Suitable for testing purposes only, as the TIBCO PSI version of the Docker image cannot be upgraded
  • Not scalable
  • Greater risk of losing data if the hosting machine crashes because of a hardware or software failure
  • Difficult to diagnose the occurrence of data loss, as no logs are available if the container is deleted
  • The entire setup can be lost if the virtual machine crashes
  • No flexibility in using different software for the component, for example, PostgreSQL cannot be replaced by Oracle

Hence, this deployment is recommended only for testing or demo purposes.