What is best approach to support 6 API gateways at 9.x versions with a single developer portal.
We have a customer at present who is running 2 Older SOA gateway nodes with one Dev portal 3.x. Customer wants to add 4 more instances with existing SOA gateway nodes making it 6. Customer is not keen on migrating to Dev portal 4.x versions .
What is the best approach without impacting performance
I'm afraid that it isn't a simple decision to make a six node cluster or three two node clusters (or two three node clusters).If the current two node cluster has to process more traffic in future and it has no room to accept more traffic, you may need to add another node to the cluster.If you're planning to publish new services, it may be an option to setup a new cluster.
I think the number of the API Developer Portal 3.x can be decided from the number of the API Gateway clusters, because the Portal 3.x doesn't support multiple Gateway tenants like 4.x.
I turned this in to a discussion type rather than a question as it was before because there is no actual "right" answer to this as what's being asked for is not actually supported by CA. Ultimately CA Support would not have an answer that's been tested and proven that would achieve this use-case, it would just be theoretical. There are actually multiple points in this scenario which are not supported, which I want to point out with added notes just for everyone's awareness:
So while the use-case is possible to achieve, it's not officially supported nor documented for such a setup. The quick of it though is this:
From a Support standpoint, I would strongly discourage the use of a database that we don't test against, and also discourage the architecture used with multiple nodes in multiple clusters across multiple data centres. Quick question: Can I ask why the customer needs so many Gateway nodes and in that particular setup? It's rare that so many Gateway nodes are actually needed to run with the Portal, so I'm curious why this is even necessary. Is it out of resources, for example? Or in other words, what is the ultimate problem they are trying to solve by adding more nodes to all their clusters?
Hi Moriyama and Dauncey ,
Thanks for your valuable suggestions regarding this setup.
Now we are planning for migration of their existing setup
Older SOA gateway Nodes ---> 9.3 version of gateway
Developer portal 3.X---> 4.X version
The customer will add two more data centers with each cluster in each data center with existing data center. Portal 4.X will still support multiple clusters and they have limited use of portal . They are not using analytics, or monetization for today. I believe wrt your 2 point putting all nodes into a single cluster and spread them across data centers is not a good idea if the latency arises. So having 3 separate clusters for different data centers as we have done it for other customers.