The ProcessRobot Servers can be configured in Active/Active group by utilizing Redis servers in order to create a highly available and scalable infrastructure. The Client tools connect to a Layer 4, TCP load balancer which is responsible to distribute the requests to the ProcessRobot Servers group.
By setting up the ProcessRobot servers in an Active/Active configuration, the installation can achieve immense scalability through horizontal scaling which not only solves computational power bottlenecks but also deals with network capacity issues.
With the above architecture we can achieve Active/Active Failover - in case of a server failure, another server automatically responds to client requests.
A group of Redis servers with Sentinels is used as a Distributed Memory Management System to ensure that all the PR Servers contain the same information regarding the components and their state. This way, in case of a ProcessRobot failure the rest of the servers in that group are able to access the information and pick up the client workload.
- To view Redis implementation and best practices visit https://redis.io.
- The information of the Redis environment (Node or Sentinels) is entered during the installation or after by editing "AppRedisSettings.config" which can be found in the Server's installation folder.
- Both Microsoft's AzureCache and Amazon's ElastiCache are supported as Redis engines.
- ProcessRobot supports High Availability on both the Client and the Server Layers. In order to enable the build-in DR capability on the Client Layer you can define multiple load balancers during the installation.