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.

Yes. Build time is definitely a pain.

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?

Apart from that, is it that the problem mentioned in another post (https://collaborate.pega.com/question/pega-robotics-studio-8-exception-attempted-read-or-write-protected-memory) might have something to do with implementation issues (which of course need a different scrutiny) and not really the number of projects afterall?

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.

Thank you for Your insightful comment! Definitely helps.

As for the post, I understand your view. The ticket information suggests precisely what you have added.