|
Saturday 02 January 2010 3:10:32 am
Just noticed the topic about siteaccess : http://share.ez.no/forums/setup-design/multiple-siteaccess-design-solution I wonder what is your advice about site access versus multiple standalone ez instance. These days I face a huge ezpublish instance (with around ~30 siteaccess, and for each one 3 translations). Every siteaccess have his own content, but nodes with multiple locations are spread within multiples siteaccess. Some workflow copy new publication from one subtree to another (every siteaccess has his own subtree I forgot to mention). It works well, so it's ok for me. If I should start this project again I really wonder If it will be more smart to use multiple ezpublish standalone instance for every siteaccess. Pros :
- maintenability
- simplicity of code (=> maintenability)
- simplicity of database management (right now everything is within the same db)
- I can disable/enable siteaccess more easily,
- All the roles, policies and workflows are centralized, it's a pain for modularity
- etc.
Cons :
- It works ! why should I change it !
- It's easy to setup multiple locations for the same node
- It's easy to copy object within subtrees.
- All the roles, policies and workflows are centralized, it's easier.
- etc.
Your advice ? your feedback ? What about server load ? thanks Happy new year, hope to meet you in Switzerland in january Pablo
Pablo Pernot
http://www.smartview.fr
http://www.areyouagile.com
|