Scaling of Order Management microservices
Previously, till the TIBCO® Order Management - Long Running 5.0.0 release, for each order management microservice node, member IDs were required to be registered in the domain member tables. The major drawback of this approach is that, whenever a new node is added to the existing cluster, you must restart the existing microservice nodes.
Now, you can scale any of the microservices as per the incoming load without restarting or configuring a separate new member. Any deployment topology can be used to and order management microservices can be started behind an external load balancer (when you choose to use SOAP over HTTP or RESTful interfaces). You can replicate microservice nodes at run time without the need to restart any of the existing microservices.
The following examples show the scaling of microservices: