How are the artifacts like workflows and subscriptions managed in a multi-node Gallery

Question

Hello,

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?

Thanks in advance.

LisaL · Answer

@pvd

Assuming that the communication among the nodes is quick then the changes made on one Gallery node should be visible on another because they all read from (and write to) the same (or a primary node of a replica set of) MongoDB.  There could be exceptions, but I would expect them to be rare because the timescale of user behavior is typically slow relative to the few milliseconds that communication would require.  If the pages have not been refreshed in some time, a user might not notice changes made by other users, however.  (Disclaimer:  I have not carried out performance testing to validate my belief, nor do I plan to.  For me, this is merely a thought experiment.)

pvd · Answer

@ianwhite that's right, we are looking at a 3 node gallery design behind a load balancer.

ianwhite · Answer

I don't think that scenario will exist unless you're placing this behind a load balancer. Normally you just scale out with workers as shown in our configuration guide. https://help.alteryx.com/20201/server/configure-server

Unless you're speaking of something else entirely that I'm not aware of.