<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr; font-family: Verdana; color: rgb(0, 0, 0); font-size: 13px;">
<div style="">Which MySQL replication (or alternate) that I would use would depend on the app. Odds are I would start with multi-master and change things if I had problems.<br>
<br>
So far as location-based stuff goes, I'd write a short Javascript that loads that uses the following logic.<br>
<br>
If $loc_cookie exists, exit<br>
Else<br>
start clock, download a 1k file from source 1, end clock, store var 1<br>
start clock, download a 1k file from source 2, end clock, store var 2<br>
Whichever var is lowest, set $loc_cookie with a 72h life.<br>
<br>
You should probably randomize whether it starts from source 1 or 2, just to make sure you're not optimizing based on DNS alone.<br>
<br>
Is it perfect? No, of course not.<br>
<br>
Is it easy and probably good enough, yep.<br>
<br>
</div>
<div><br>
<div style="font-family: Tahoma; font-size: 13px;">
<div style="font-family: Tahoma; font-size: 13px;">
<div style="font-family: Tahoma; font-size: 13px;"><font style="font-family: Courier New;" color="#888888" size="1">-Josh More, CISSP, GIAC-GSLC, GIAC-GCIH, RHCE, NCLP<br>
<a href="mailto:morej@alliancetechnologies.net" target="_blank"><span class="il">morej@alliancetechnologies.net</span></a>
<br>
515-245-7701 </font>
<div style="font-family: Tahoma; font-size: 13px;"></div>
</div>
</div>
</div>
</div>
<div style="font-family: Times New Roman; color: rgb(0, 0, 0); font-size: 16px;">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF584657"><font color="#000000" size="2" face="Tahoma"><b>From:</b> cialug-bounces@cialug.org [cialug-bounces@cialug.org] on behalf of Matthew Nuzum [newz@bearfruit.org]<br>
<b>Sent:</b> Friday, October 22, 2010 14:45<br>
<b>To:</b> Central Iowa Linux Users Group<br>
<b>Subject:</b> Re: [Cialug] multi-national web app decisions<br>
</font><br>
</div>
<div></div>
<div>
<div class="gmail_quote">On Fri, Oct 22, 2010 at 12:39 PM, Matthew Nuzum <span dir="ltr">
<<a href="mailto:newz@bearfruit.org" target="_blank">newz@bearfruit.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
If you were building a web app from scratch and you wanted it to be fast world-wide, what architectural decisions would you make? Using Linux, of course. In my case I have access to inexpensive DC space in the US and Europe. When a user makes a preference change
in EU it should be changed everywhere, but it does not need to be instantaneous. As a matter of fact, what I have in mind should favor perceived front-end performance. I mean I'd prefer not to use a tool that adds 20ms of latency while data is replicated to
another location.</blockquote>
<div> </div>
</div>
Let me be more specific, would you use MySQL multi-master replication, standard replication or would you use some other database technology?
<div><br>
</div>
<div>Also, what would you do to direct people to a location near them, would you use a DNS service , would you run your own DNS servers and configure them to do geo based serving, or would you use something else?<br clear="all">
<br>
-- <br>
Matthew Nuzum<br>
newz2000 on freenode, skype, linkedin, <a href="http://identi.ca" target="_blank">
identi.ca</a> and twitter<br>
<br>
"An investment in knowledge pays the best interest." -Benjamin Franklin <br>
<br>
</div>
</div>
</div>
</div>
</body>
</html>