Hi Vincent, Thanks for your reply.
I have some comments below Thanks. On Tue, Jul 20, 2010 at 10:48 AM, Vincent de Lau <vinc...@delau.nl> wrote: > > > I don't have enough experience to advice on this, however: MySQL also > supports a cluster mode, NDB. It should work transparently but will spread > the storage and query workload across multiple nodes. > Regarding the NDB so far the requirements that I've read (i.e the database should be in memory) invalidate it as a solution for me. I am not sure if I understood it correctly but I'd love to read about other's experience with that. > > > Do you need ZF when accessing the files or are they purely static? If they > are completely static, I'd consider creating separate nodes for static > content. Replication can be done using RSYNC, but maybe a network file > system might be useful. Redundancy might become a problem however. > > One of the apps allow the admin of the site to upload photos and attach tags, description text to it. So the files are static (not database/dynamic generated). In my experience (and from other testimonials) NFS seems to be a problem when a node looses the connection (hence the replication issue that you've stated). > Another solution might be to have a 404 handler that triggers an update > somehow. For some systems we use, files are stored in the database and > cached on the node on first access. > > The 404 causing a fetch from the binary (static) file is interesting and I'll have to investigate but it surely solves one part of the problem that is the text (from the database) be in sync while the file it references is not (well at least for the most part). Do you have any sample code that you can share so I can start testing with it? > > I hope these few cents are helpful. > > Surely they were... > Vincent de Lau > vinc...@delau.nl > >
