Earnie-<br><br>I did not say that we store data on the web server -- in fact, we always keep the two separate. I simply said that we place the datadase server on the same network switch (in reality, on the same rack) as the web server, to avoid latency issues.<br>
<br>We actually use a load-balanced web server connected to replicated MySQL.<br><br>- Ken<br><br><br><div class="gmail_quote">On Fri, May 2, 2008 at 9:13 AM, Earnie Boyd <<a href="mailto:earnie@users.sourceforge.net">earnie@users.sourceforge.net</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Quoting Ken Rickard <<a href="mailto:agentrickard@gmail.com" target="_blank">agentrickard@gmail.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Earnie-<br>
<br>
(I work for one of those corporations.)<br>
<br>
But that 100 ms latency would only affect non-Drupal data being pulled into<br>
the application -- say an inventory database housed in Connecticut with a<br>
web app server in Georgia (actual example).<br>
<br>
</blockquote>
<br></div>
I would give away too much to explain in detail but we store 100K rows of usage data in any given minute. The account holders can review those rows real time including months of history. The set of data is too large and too sensitive to store on the web server. Just one example. Lots of data everywhere. I can't think that any of our data is actually sitting on the web servers except for internal use sites.<div>
<div></div><div class="Wj3C7c"><br>
<br>
Earnie -- <a href="http://for-my-kids.com/" target="_blank">http://for-my-kids.com/</a><br>
-- <a href="http://give-me-an-offer.com/" target="_blank">http://give-me-an-offer.com/</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ken Rickard<br><a href="mailto:agentrickard@gmail.com">agentrickard@gmail.com</a><br><a href="http://ken.therickards.com">http://ken.therickards.com</a>