[opencms-dev] 3xOpenCMS sharing one Database, yes or no ?

[Jose Ignacio Yarza]

Excerpt from here:

 

http://comments.gmane.org/gmane.comp.cms.opencms.devel/38158

 

Achim Westermann wrote this a month ago:

 

“(
)My current company spent again

and again and again and again and again efforts to circumvent buying

ocee. We set up cronjobs to delete static export files on slave servers

(which costs additional performance), I - as a former OpenCms developer

with some insight on the internals - coded a jsp to flush the caches on

the slave instances. And on a weekly turn someone passes by to let me

request that special jsp to have the cache flushed. And then they tried

to deactivate the OpenCms cache and ran into performance issues. Putting

an external cache in front of a clustered OpenCms will even get you

deeper into the mud.

And then some editor did forget or not know (as they were new to our

company) that an OpenCms cluster slave will not know about changes

witout ocee. Did not contact me and had troubles because changes were

not propagated. And again and again and again and again and again and

again I keep on manually flushing the cache on the slave cluster servers

if some editor knew that we had this "cluster - issue".

Sum up: Those 3500 bucks spent on ocee cluster... we already lost a lot

more of money to circumvent buying that. And we will never achieve a

better solution because Alkacon did work on that for many years and

constantly is fixing bugs concerning ocee cluster. This is not a fanboi

advertisement. It's just my opinion: You will never save money by trying

to implement your own OpenCms cluster. The only thing you will achieve

is to increase your level of maintenance and time to web.

In case you don't know what problems will arise when running OpenCms in

a cluster without ocee feel free to answer.

“

 

What Achim says, which I can completely identify with, would be aligned with
the official word?

 

Thanks

 

 

De: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org]
En nombre de Jose Ignacio Yarza
Enviado el: miércoles, 11 de septiembre de 2013 11:13
Para: 'The OpenCms mailing list'
Asunto: [opencms-dev] 3xOpenCMS sharing one Database, yes or no ?

 

Hi List,

 

 

This is an important issue that I would like to share with and if possible
get from you some valuable and informed feedback.

 

We have setup in a production environment three opencms (8.5) instances over
three independent JBoss (not clustered), sharing one same Oracle (11g)
database. There is an Apache web server balancig between the three JBoss
instances. This environment is read-only, there is not content management
concurrency, only dynamic page generation for a website.

 

The issue is that there is a performance degradation that does not happen in
our other single-instance environments, which are setup in the standard way
(named development and test).

 

I know about the potential problems with the data access parts managed
inside the three JBoss instances, where we'd find three different connection
pools, Solr indexes not in sync, flex cache,...

 

Question: So, Is it an affordable task to tune up this setup and make it
work fine? Do we need OCEE? Is the pain worth it being a read only
environment? Wouldn't be a much better solution, in this read-only scenario,
using static export altogether? 

 

I know this is a recurrent matter,  and have read good information but also
some divagation about it. I have my own opinion (go static), but it seems
not enough for politicians, that’s why I am asking here. Any official advice
on the overall idea is also very welcome. Thank you for your suggestions.

 

 

 

Jose Ignacio Yarza

Open Sistemas

Tel: 649 157 537

 

logo_open

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20130911/980badd9/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 7887 bytes
Desc: not available
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20130911/980badd9/attachment.jpg>