您使用 AWSDBProxy 吗? 横向扩展时是否会影响性能?
似乎唯一讨论在 Rails 站点中使用 Amazon SimpleDB 的教程是使用 AWSDBProxy...就我个人而言,考虑到下面典型 Rails 站点的服务器布局(使用 AWSDBProxy),我发现这与扩展是违反直觉的:
插件位于:http://agilewebdevelopment.com/plugins/aws_sdb_proxy
图片位于:http://www.freeimagehosting.net/uploads/91be4e0617.png
如您所见,即使我们添加更多杂种,我们有两个问题。
- 我们的单点故障远不如我们的负载均衡器稳定
- 我们必须通过这台WEBrick服务器强制我们的所有信息
解决方案当然是添加更多AWSDBProxies...但为什么不呢然后只需在一个类中使用以下代码,一起跳过代理?
service = AwsSdb::Service.new(Logger.new(nil),
CONFIG['aws_access_key_id'],
CONFIG['aws_secret_access_key'])
service.query(domain, query)
所以我的意思是,如果您正在使用 AWSDBProxy,那么您使用它的理由是什么? 如果你确实在使用它,你的表现如何? 如果您有确切的数字,那就更感激了!
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):
Plugin here: http://agilewebdevelopment.com/plugins/aws_sdb_proxy
Image here: http://www.freeimagehosting.net/uploads/91be4e0617.png
As you can see, even if we add more mongrels, we have two problems.
- We have a single point of failure far less stable than our load balancer
- We have to force all our information through this one WEBrick server
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?
service = AwsSdb::Service.new(Logger.new(nil),
CONFIG['aws_access_key_id'],
CONFIG['aws_secret_access_key'])
service.query(domain, query)
So what I'm getting at, is if you are 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!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我没有使用它,也没有听说过它,但这是我认为合理的理由。
I'm not using it, nor have I ever heard of it, but this is what I would think are reasonable reasons.