<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
I’m new to shared file systems and horizontal cloud scaling.<br>
<br>
I have already played with auto-scaling on aws/ec2. In term of
spawning a destroying and I can achieve that. <br>
<br>
I just want to some advice of how best implement syncing for web
files, infrastructure, data, etc.<br>
<br>
I have pretty much decided to put the database side of things on a
private instance. <br>
I'll worry about db clustering later I’m not to bothered about this
not, because the software supports it.<br>
<br>
It seems logical to put the web folder / application layer on a
shared file system, maybe some configuration too.<br>
<br>
What I'm really unsure about is how to ensure that the current
system is up to date and the configuration tweaked for the physical
specs.<br>
<br>
How do people typically approach this? I'm guessing it not always
viable to have a shared file system for everything.<br>
<br>
Is the approach a disciplined one? Where say I have development
instance for infrastructure changes. <br>
Then there is a deployment flow where production instances are
somehow refreshed without downtime. <br>
<br>
Or is there some other approach?<br>
<br>
I notice on sites like yahoo, things are often noticeably unsynced,
mostly on the data front, but also other things. <br>
This would be unacceptable in my case.<br>
<br>
I appreciate any help I can get regarding this. <br>
<br>
My typical load is from php-fpm/nginx processes, mysql bellow this.
<br>
<br>
Should the memory cache also be separated, or as I think it is quite
good for this to be divided up with the infrastructure to support
each public instance individually? <br>
<br>
Paul<br>
</body>
</html>