Databases
StackOverflow2013
Postsdbo
POAre you using AWSDBProxy? Is there a performance hit when scaling out?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAre you using AWSDBProxy? Is there a performance hit when scaling out?
    text
    copied!<p>After a down vote, I humbly realized that my post was an enormous <em>rant</em>. So I've edited it and summed this down to just the question I'd really like to know. I apologize for my brash comments prior to this edit ;) </p> <p>It seems that the only tutorials out there talking about using Amazon's SimpleDB in a rails site are using AWSDBProxy... Personally, I find this counter-intuitive to scaling out, considering the server layout of a typical Rails site below (using AWSDBProxy):</p> <p>Plugin here: <a href="http://agilewebdevelopment.com/plugins/aws_sdb_proxy" rel="nofollow noreferrer">http://agilewebdevelopment.com/plugins/aws_sdb_proxy</a></p> <p>Image here: <a href="http://www.freeimagehosting.net/uploads/91be4e0617.png" rel="nofollow noreferrer">http://www.freeimagehosting.net/uploads/91be4e0617.png</a></p> <p>As you can see, even if we add more mongrels, we have two problems.</p> <ol> <li>We have a single point of failure far less stable than our load balancer</li> <li>We have to force all our information through this one <em>WEBrick server</em></li> </ol> <p>The solution is, of course, to add more AWSDBProxies... but why not then just use the following code in say, a class, skipping the proxy all together?</p> <pre><code>service = AwsSdb::Service.new(Logger.new(nil), CONFIG['aws_access_key_id'], CONFIG['aws_secret_access_key']) service.query(domain, query) </code></pre> <p>So what I'm getting at, is if you <em>are</em> using AWSDBProxy, what are you justifications for it? And if you are indeed using it, what is your performance like? If you have hard numbers, this would be even more appreciated!</p> <p>Thanks!</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload