[Typo3-dev] Distributet Typo3 site, how to approach this?

[Arco]

I think there are a few things:

core-db      : can be replicated from a master.
tmp-db       : is probably a per server part.
FE user-data : can be a problem to update.

img/doc files: can be replicated in server ways.
tmp-files    : per server.

Clustering, if I read correctly, is not the best option if the link between the nodes is slow.

Georg Rehfeld <georg.rehfeld at gmx.de> wrote ..
> Dear Martin,
> 
> thanks for your quick response and suggestion.
> 
> > You'll want to look at distribution at the database level. MySQL does
> > replication[1], and if I'm not mistaken, it works quite well.
> 
> Looking into this direction it might also be a worth to look at MySQL
> clustering, which should be available even in commercial quality
> soon:
> 
> http://www.mysql.com/products/cluster/
> 
> As far as I can see with a cluster there is no dedicated master any more
> from the perspective of the application (the different Typo3
> installations).
> 
> However, with both approaches (simple replication or clustering), what
> is not replicated are all files stored in the filesystem: images,
> uploaded documents etc. So e.g. the indexed search would still be unable
> to find all relevant documents. Also the complete site could not be
> navigated from  a single daughter server: e.g. the images to display
> and the documents to download would only be present for the daughter at
> hand and missing for all others. This might possibly be solved with the
> URL rewriting. But the indexed search problem remains, doesn't it?
> 
> Best regards
> 
> Georg
> -- 
>   ___   ___
> | + | |__    Georg Rehfeld      Woltmanstr. 12     20097 Hamburg
> |_|_\ |___   georg.rehfeld.nospam at gmx.de    +49 (40) 23 53 27 10
> 
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev