This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
We are looking at a multi-node load balanced Gallery design and have a question around how the artifacts like subscriptions (private studios), their API key/secrets and the workflows within the subscriptions are managed.
If we have to create a studio and deploy workflows, does that have to be done on all Gallery nodes? Also if the subscriptions are different on these nodes, does that mean the key/secrets are different?
Typically when a multi-node gallery is mentioned, it's set up in a way that has one controller and multiple workers. When this is the case, you utilize a tag feature within the System Settings to specify workflows to run on a specific worker. In that scenario, you don't end up diverging your workflows or subscriptions as they will all still use the same instance of mongodb which stores that data.
Is it safe to assume that if User1 hits Gallery-Node1, creates a subscription and publishes workflows and if a different User2 hits Gallery-Node2, the same workflows and subscription are visible to User2? Are the workflows stored (may be as xml data) in MongoDb when they are published? and subscription API key/secret are stored in MongoDb instance as well?
We are validating if there is a need to create/publish these artifacts on multiple gallery nodes. We are aware of the tagging functionality for sending the workloads to different worker nodes and are planning to leverage that.