Transparent redundancy with .NET server
Posted: 26 Jan 2016, 21:41
Dear Support Team,
I am developing an OPC UA Server using you .NET Server SDK and would like to know the best way to implement transparent redundancy.
Reading through other posts, I found information that you have or are working on a C++ package to implement transparent redundancy. Is this also available for .NET?
If we have multiple OPC UA servers running behind a load balancer that balances incoming connections, would anything addition be necessary?
I assume that the session would not change between servers once established but any new connection would go to a random server. All servers share the same underlying system so all node data would be the same.
So far I looked at:
http://forum.unified-automation.com/topic611.html
http://forum.unified-automation.com/topic159.html
http://forum.unified-automation.com/topic1630.html
http://forum.unified-automation.com/topic1371.html
We estimate that our setup will have to handle approximately 100 simultaneous clients and 150,000 nodes. Each client will subscribe to only a few hundred nodes.
Sincerely,
Jonathan
I am developing an OPC UA Server using you .NET Server SDK and would like to know the best way to implement transparent redundancy.
Reading through other posts, I found information that you have or are working on a C++ package to implement transparent redundancy. Is this also available for .NET?
If we have multiple OPC UA servers running behind a load balancer that balances incoming connections, would anything addition be necessary?
I assume that the session would not change between servers once established but any new connection would go to a random server. All servers share the same underlying system so all node data would be the same.
So far I looked at:
http://forum.unified-automation.com/topic611.html
http://forum.unified-automation.com/topic159.html
http://forum.unified-automation.com/topic1630.html
http://forum.unified-automation.com/topic1371.html
We estimate that our setup will have to handle approximately 100 simultaneous clients and 150,000 nodes. Each client will subscribe to only a few hundred nodes.
Sincerely,
Jonathan