Multi-Pod Cluster Deployment

Multi-pod cluster deployment is more complex than the single pod deployment. It is also more resilient to hardware failures and is suitable for horizontal scaling.

TIBCO FSI attains high availability in this deployment due to multiple instances of TIBCO FSI servers in different pods. If a pod crashes and stops working, the remaining pods in TIBCO FSI service are still available to service the incoming requests. The remaining pods continue to function until a replacement pod is started by the Kubernetes master. The data remains safe as the database runs on a different pod under a different exposed service.
Note: To make a database (PostgreSQL or Oracle) or server (TIBCO FTL or Enterprise Message Service™) highly available, you must deploy them in high availability mode. For more information on high availability deployment of PostgreSQL, Oracle,TIBCO FTL, or Enterprise Message Service™, refer to the respective documentation.

The TIBCO FSI GUI is accessed using the IP address of TIBCO FSI service. TIBCO FSI service is a Kubernetes object. TIBCO FSI service routes the request to an available FSI Pod, for example, http://<ip address of FSI Service>:8080/fsi-server.