Possibilities to use multiple DB's & to split up an EZ Publish installation?

Next topic

Author	Message
Ronald Kools	Tuesday 08 March 2005 6:09:28 am I have 2 questions, on which I have already found some information, but not quite what I am looking for. As it is rather trivial to have the correct information about this (as we will decide between EZ Publish and Typo3 depending on the result), I hope someone can help me out here. <b>Q1: Is it possible to split a EZ Publish installation?</b> We'd like to secure our admins by moving them to a dedicated server. In other words: the admin of EZ Publish should be installed on a different machine than the frontend. Does anyone know whether this is possible or do we have to install EZ Publish on two machines using the same database and then disable the admin on the machine with the frontend? <b>Q2: Is it possible to use multiple databases?</b> We might want to READ a diffent database than the one you WRITE to. In other words: a SELECT is done on DB 1 while an INSERT is done on DB 2. Is this possible with EZ Publish? Thanks for your answers.
Björn Dieding@xrow.de	Tuesday 08 March 2005 7:46:53 am Here are my answers Q1: yes Q2: Well this is a little complicated since the frontend requires write access for permissions and other stuff too. If this question is about security you should try to do a static dump of your website. If this question is about load you should try to use a mysql cluster. Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs Looking for hosting? http://hostingezpublish.com ----------------------------------------------------------------------------- GMT +01:00 Hannover, Germany Web: http://www.xrow.com/
Ronald Kools	Tuesday 08 March 2005 8:03:15 am Thank you! Q2 is related to load balancing system we are planning to use. It could have some advantages to be able to separate what you see and what you can edit. We'll have a look at mysql clusters too... thanx!

Author

Message

Tuesday 08 March 2005 6:09:28 am

I have 2 questions, on which I have already found *some* information, but not quite what I am looking for. As it is rather trivial to have the correct information about this (as we will decide between EZ Publish and Typo3 depending on the result), I hope someone can help me out here.

<b>Q1: Is it possible to split a EZ Publish installation?</b>

We'd like to secure our admins by moving them to a dedicated server. In other words: the admin of EZ Publish should be installed on a different machine than the frontend. Does anyone know whether this is possible or do we have to install EZ Publish on two machines using the same database and then disable the admin on the machine with the frontend?

<b>Q2: Is it possible to use multiple databases?</b>

We might want to READ a diffent database than the one you WRITE to. In other words: a SELECT is done on DB 1 while an INSERT is done on DB 2. Is this possible with EZ Publish?

Thanks for your answers.

Björn Dieding@xrow.de

Tuesday 08 March 2005 7:46:53 am

Here are my answers

Q1: yes

Q2: Well this is a little complicated since the frontend requires write access for permissions and other stuff too.

If this question is about security you should try to do a static dump of your website.

If this question is about load you should try to use a mysql cluster.

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Ronald Kools

Tuesday 08 March 2005 8:03:15 am

Thank you!

Q2 is related to load balancing system we are planning to use. It could have some advantages to be able to separate what you see and what you can edit.

We'll have a look at mysql clusters too... thanx!

eZ debug

Timing:	Jan 19 2025 01:00:52
Script start
Timing:	Jan 19 2025 01:00:52
Module start 'layout'
Timing:	Jan 19 2025 01:00:52
Module start 'content'
Timing:	Jan 19 2025 01:00:52
Module end 'content'
Timing:	Jan 19 2025 01:00:52
Script end

Main resources:

Total runtime	0.0180 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0067	589.6563	152.6875
Module start 'layout'	0.0067	0.0025	742.3438	39.5547
Module start 'content'	0.0092	0.0068	781.8984	89.3672
Module end 'content'	0.0160	0.0020	871.2656	34.3047
Script end	0.0180		905.5703

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	15.1093	14	0.0002
Check MTime	0.0013	7.2110	14	0.0001
Mysql Total
Database connection	0.0008	4.5814	1	0.0008
Mysqli_queries	0.0029	16.2785	3	0.0010
Looping result	0.0000	0.1112	1	0.0000
Template Total	0.0016	8.7	1	0.0016
Template load	0.0009	4.7866	1	0.0009
Template processing	0.0007	3.9154	1	0.0007
Override
Cache load	0.0006	3.3606	1	0.0006
General
dbfile	0.0016	8.8198	8	0.0002
String conversion	0.0000	0.0543	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs