Multiple Agents for Disparate Projects?
Given several disparate projects, each with its own dependencies (installed packages and custom python modules), does it make sense to run:
A. One agent pre project
B. One agent to service all the projects?
12/11/2020, 7:20 PM
Hi @jack - either model is fine but I'd recommend the latter where your agents serve more general service patterns (resources, environments etc), assuming your flows have disparate requirements, rather than having a single agent.
12/11/2020, 7:23 PM
Do you mean "if the resources and environments are similar, use a single agent"?
12/11/2020, 7:28 PM
Well it depends, you might separate your agents by environment - for example dev and prod - where the agent running in prod is on a large machine with lots of resources and uptime checks etc and the dev one less so - so you could then label flows (or specific runs of a flow!) based on where you want something to run
It boils down to: there's not really a correct answer, it's what makes the most sense for your infrastructure and the types of requirements your flows have
I'd say to start with a single agent and scale out as needed