Whats the impact of large number of projects in a Robotic Solution?
How and in what way does having large number of projects inside a Robotic solution impact its performance?
We understand that it results in copying the OpenSpan specific build artifacts across projects, making the build process slower and the project folder getting huge in size. But, the same project, when deployed and loaded expands to a smaller local memory footprint. The way it impacts memory consuption and overall slowness while while the robot runs is unclear.
The only thing that multiple projects affects is the build time. The memory footprint of extra projects versus including all of the same components in one project is minimal to none (at runtime) in my experience.
I was thinking that it might also have a negative impact when we run such a solution, specifically due to the initialization of artifacts present in each project. But, your experience suggests otherwise.
In that sense, is the number of projects in a solution is more of a suggested convention/best practice, that probably needs discretion depending on the requirement at hand?
Separating functionality into separate projects is really not optional. It is best practice and allows multiple developers to collaborate. I would always create separate projects for separate functionality (usually at least one per adapter).
I cannot speak to the other post as I did not investigate, but it seems as though it was looked at by support and found that there were simultaneous automations running and not the problem simply being the number of projects.