SiteAccess vs multiple standalone ez instance, pros & cons, feedback

« 
Previous topic
|
Setup & design
|
Next topic
 »
Author Message

Pablo Pernot

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

Nicolas Pastorino

Monday 01 February 2010 8:26:03 am

Hi Pablo,

For security purposes a total isolation of applications may be required. Meaning no single line of code, nor any resource shoul dbe shared. In this case you need to have separate instances.
As well, when one eZ Publish instance hosts say 2 applications, which have different evolution paces, the tie-in of the 2 applications being on the same instance may reduce flexibility and prevent from having 2 very different evolution/maintenance paces.

I think we should enhance the initial thread with these considerations, should bring up useful points: http://share.ez.no/forums/setup-d.../multiple-siteaccess-design-solution

My 2 cents,
cheers,

--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter: http://twitter.com/ezcommunity

t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye
Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 02:08:26
Script start
Timing: Jan 18 2025 02:08:26
Module start 'layout'
Timing: Jan 18 2025 02:08:26
Module start 'content'
Timing: Jan 18 2025 02:08:26
Module end 'content'
Timing: Jan 18 2025 02:08:26
Script end

Main resources:

Total runtime0.8336 sec
Peak memory usage4,096.0000 KB
Database Queries54

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0057 589.5703153.4844
Module start 'layout' 0.00570.0022 743.054739.4375
Module start 'content' 0.00790.8245 782.4922543.2422
Module end 'content' 0.83240.0012 1,325.734412.0938
Script end 0.8336  1,337.8281 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00310.3695160.0002
Check MTime0.00130.1519160.0001
Mysql Total
Database connection0.00060.072910.0006
Mysqli_queries0.780893.6600540.0145
Looping result0.00050.0562520.0000
Template Total0.805296.620.4026
Template load0.00200.238720.0010
Template processing0.803296.357920.4016
Template load and register function0.00030.031910.0003
states
state_id_array0.00100.120910.0010
state_identifier_array0.00120.145020.0006
Override
Cache load0.00170.2007370.0000
Sytem overhead
Fetch class attribute can translate value0.00150.174220.0007
Fetch class attribute name0.00150.184640.0004
XML
Image XML parsing0.00140.169020.0007
class_abstraction
Instantiating content class attribute0.00000.000940.0000
General
dbfile0.00120.1472220.0001
String conversion0.00000.000940.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
2content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
2content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
6content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
2content/datatype/view/ezxmltags/li.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/li.tplEdit templateOverride template
2content/datatype/view/ezxmltags/ul.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/ul.tplEdit templateOverride template
2content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 18
 Number of unique templates used: 8

Time used to render debug report: 0.0001 secs