Can someone help me to understand the advantages and disadvantages of Domain orchestrator and Clustered domain orchestrator, the main difference between these two Process automation Setups.
In a nutshell this is a stand alone server vs a load balanced set of servers, and cluster may not be the proper terminology here. A clustered domain orchestrator is 2 or more Process Automation servers behind a load balancer (F5, NGiNX, Apache are the three we have certified with). If you have a single domain orchestrator and you are beginning to notice a performance decrease and your workload is increasing, you may want to consider a load balanced setup. This is just one of the ways to help with performance, but depending on the server resources may not be the only issue.
Advantages and disadvantages are going to be on a case by case basis. If you don't really require a second Process Automation node, then server management would fall under the disadvantage column.
The obvious advantage is for a fail-over situation. If server A suddenly becomes unavailable, all work will be processed on server B, and there won't be an interruption in service - unless of course your workload is so heavy that one server cannot handle the load.
All of this is something that you may want to discuss with CA Services in an architectural and process review.
There isn't a "one answer fits all" scenario for CA Process Automation, but I count that under the advantage column
I just had a conversation with Michael Niebuhr this week about this.
Basically, looking at this part of docops: System Components - CA Process Automation - 04.3.02 - CA Technologies Documentation
You can see that when you add a cluster node to the domain orquestrator, it will spread the load and add performance to Process Automation. That's the difference of having a cluster of a application or not.
Under performance, you can check for Performance and Scalability Benchmarking - CA Process Automation - 04.3.02 - CA Technologies Documentation
Hope it helps
Retrieving data ...