7.
Miscellaneous Notes on Architecture (by Lupi)
Up one level
Here is a general sketch of the architecture that I expect you will be using for Do2gether and future Draft2gether (if it will be developed in Plone).
• Apache will act as a gateway and proxy, serve static content (javascript frameworks, CSS stylesheets, user interface images), translate addresses like org1.d2g.com into requests to your Zope instances (using mod_rewrite).
• There will be one production Zope instance per CPU in your servers.
• These Zope instances may be distributed to one or more physical hosts, you will add boxes as your users grow.
• Each Zope instance will accommodate one or more Plone sites (Do2gether, Draft2gether). Each Plone site will serve a single organization. You should create a master/template installation for each of your products. Zope allow you to easily clone that template directly from the Web, making it very easy to add a new organization.
• When a Plone site becomes too big and you need to scale up, you will move it to a separate Zope instance on a new box.
I hope that these notes will be useful.
Yours Truly,
Roberto Lupi