Hi
In our (limited) experience, here are pros and cons of using a single
instance:
+ better use of server resources (RAM, CPU) this is quite important;
+ single global configuration (servlet container, Java VM, Apache or
other frontend...)
+ being forced to deploy global updates (to Cocoon configuration,
custom components, etc.) on all apps (projects), this is good for
security and performance updates;
- slower, more expensive global updates (you have to test all apps
on the same Cocoon)
- sometimes you have to go through loops to introduce new features
while maintaining compatibility with older apps.
All in all, we are quite happy with a "hybrid" approach: we keep all
apps in the same Cocoon, until we need such new features or such a
different Cocoon configuration to warrant a branch to a new "major
version" of our configuration. So we have something like 30 apps
split among 3 Cocoons. The next update to one of the older projects
will trigger a switch to the newest Cocoon configuration, and so on.
HTH
Tobia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
