<div class="gmail_quote">On Fri, Oct 22, 2010 at 12:39 PM, Matthew Nuzum <span dir="ltr"><<a href="mailto:newz@bearfruit.org">newz@bearfruit.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;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>