Scaling XPages across servers
In China everything is bigger. The wall is longer then elsewhere and companies, catering to 1.3 billion people have a lot of employees. I'm currently working with our experts from the China development lab to figure out, based on discussions with customers and business partners, how to scale XPages when one server is not enough.
When it comes to architecture, opinions are a dime a dozend. We had "experts" chipping in who would happily split XPages server and NSF server into two introducing network latency between the two. Others are convinced, that only RDBMS is the real thing. Since Domino 8.5.3 happily connects to an RDBMS, the question became more interesting (not that we didn't have options before). As usual the devil is in the details, which in case of Domino would be Multi-Value fields and Reader and Author protection.
We are planning to have 2 servers and test them in various configurations to see whar are the performance ramifications:
When it comes to architecture, opinions are a dime a dozend. We had "experts" chipping in who would happily split XPages server and NSF server into two introducing network latency between the two. Others are convinced, that only RDBMS is the real thing. Since Domino 8.5.3 happily connects to an RDBMS, the question became more interesting (not that we didn't have options before). As usual the devil is in the details, which in case of Domino would be Multi-Value fields and Reader and Author protection.
We are planning to have 2 servers and test them in various configurations to see whar are the performance ramifications:
-
XPages and NSF Server
-
XPages Cluster
-
XPages and RDBMS
Posted by Stephan H Wissel on 08 September 2011 | Comments (3) | categories: XPages