They don't have anything like SQS but there are a few good services that you may be able to take advantage of:
Cloud Files
With AkamaiCDN - push all your static stuff right out to your clients (I'm in Gold Coast Australia and cloud files public content comes to me from some server in Brisbane (13 msec vs 250 msec ping times for USA servers) and due to the effect of distance on download speed - faster download times for your users, plus absolutely no clogging the pipes on the web server during the Christmas rush.
The way I use it is:
I create a Cloud files container; this gets a unique hostname.
I create a CNAME DNS record (for example: cdn.supa.ws) pointing to that unique hostname.
I use cloudfuse to mount the directory both on my cloud server and on my home linux box.
Then just copy or upload files straight to that directory, then serve them from http://cdn.yourdomain.com
Load balancers as a service
http://www.rackspace.com/cloud/cloud_hosting_products/loadbalancers/ - Basically a bunch of Zeus load balancers that you can use to push requests to your back end servers. Cool because they're API programmable, so you can scale on the fly and add more backend servers as needed. They also have nice weighting algorithms, so you can send more traffic to certain servers if needed.
Internal VLAN
I would recommend using the 'internal IPs' (10.x.y.z) (the eth1 interface) for message queuing and DB data between Cloud Servers as they give you a higher outgoing bandwidth cap.
Outgoing Bandwidth (speed) caps:
256 MB Ram - 10 Mb/s eth0 - 20 Mb/s eth1
512 MB Ram - 20 Mb/s eth0 - 40 Mb/s eth1
1 GB Ram - 30 eth0 - 60 Mb/s eth1
2 GB Ram - 40 eth0 - 80 Mb/s eth1
4 GB Ram - 50 eth0 - 100 Mb/s eth1
8 GB Ram - 60 eth0 - 120 Mb/s eth1
15.5 GB Ram - 70 eth0 - 140 Mb/s eth1
eth1 is called an Internal VLAN, but it is shared with other customers, so best to firewall off your eth1 as well as your eth0, for example only allow mysql connections from your Cloud Servers; and if you have really sensetive stuff maybe use myqsl with ssl, just in case :)
Beanstalkd just rocks- Tubes function as pub-sub and can just work like a charm on any cloud vendor. 3-7 minutes to setup. Blazingly fast since uses memcache like queue.
You can write workers in any language you chose from. You cannot go wrong with this one.
发布评论
评论（3）
他们没有类似 SQS 的服务，但您可以利用一些不错的服务：
云文件
带有 Akamai CDN - 将所有静态内容直接推送给您的客户（我在澳大利亚黄金海岸，云文件公共内容从某个服务器发送给我）在布里斯班 (13毫秒与美国服务器 250 毫秒 ping 时间）以及由于 距离对下载速度的影响 - 为您的用户提供更快的下载时间，而且在圣诞节高峰期间绝对不会堵塞网络服务器上的管道。
我使用它的方式是：
加载 它们平衡器即服务
http://www.rackspace.com/cloud/cloud_hosting_products/loadbalancers/ - 基本上是一堆 Zeus 负载均衡器，您可以使用它们将请求推送到您的后端服务器。很酷，因为它们是 API 可编程的，因此您可以动态扩展并根据需要添加更多后端服务器。他们还有很好的加权算法，因此您可以根据需要向某些服务器发送更多流量。
内部 VLAN
我建议使用“内部 IP”(10.xyz)（eth1 接口）进行云服务器之间的消息队列和数据库数据，因为它们为您提供更高的传出带宽上限。
传出带宽（速度）上限：
eth1 称为内部 VLAN，但与其他客户共享，因此最好防火墙关闭您的 eth1 和 eth0，例如仅允许来自云服务器的 mysql 连接；如果您有真正有意义的东西，可以将 myqsl 与 ssl 一起使用，以防万一:)
MySQL 作为服务
还有一个 MySQL 作为服务 私人测试版。我还没有尝试过，但看起来它有很多潜在的酷感： http://www.rackspace.com/cloud/blog/2011/12/01/announcing-the-rackspace-mysql-cloud-database-private-beta/
They don't have anything like SQS but there are a few good services that you may be able to take advantage of:
Cloud Files
With Akamai CDN - push all your static stuff right out to your clients (I'm in Gold Coast Australia and cloud files public content comes to me from some server in Brisbane (13 msec vs 250 msec ping times for USA servers) and due to the effect of distance on download speed - faster download times for your users, plus absolutely no clogging the pipes on the web server during the Christmas rush.
The way I use it is:
Load balancers as a service
http://www.rackspace.com/cloud/cloud_hosting_products/loadbalancers/ - Basically a bunch of Zeus load balancers that you can use to push requests to your back end servers. Cool because they're API programmable, so you can scale on the fly and add more backend servers as needed. They also have nice weighting algorithms, so you can send more traffic to certain servers if needed.
Internal VLAN
I would recommend using the 'internal IPs' (10.x.y.z) (the eth1 interface) for message queuing and DB data between Cloud Servers as they give you a higher outgoing bandwidth cap.
Outgoing Bandwidth (speed) caps:
eth1 is called an Internal VLAN, but it is shared with other customers, so best to firewall off your eth1 as well as your eth0, for example only allow mysql connections from your Cloud Servers; and if you have really sensetive stuff maybe use myqsl with ssl, just in case :)
MySQL as a service
There is also a MySQL as a service private beta. I haven't tried it yet, but looks like it has a lot of potential coolness: http://www.rackspace.com/cloud/blog/2011/12/01/announcing-the-rackspace-mysql-cloud-database-private-beta/
Rackspace 不提供托管排队系统。
我已经在他们的云服务器上运行 RabbitMQ 两年多了，一切都很好。
我还没有尝试过集群，所以我不知道设置起来有多容易在那里，也不知道它在他们的环境中有多稳定。
Rackspace don't offer a hosted queuing system.
I've been running RabbitMQ on their Cloud Servers for more than 2 years and things are good.
I haven't tried clustering though so I don't know how easy it would be to setup over there, nor how stable it would be in their environment.
Beanstalkd 太棒了——Tube 可以作为发布-订阅的功能，并且可以在任何云供应商上发挥作用。 3-7 分钟即可完成设置。由于使用类似队列的内存缓存，速度非常快。
您可以用您选择的任何语言编写工作程序。这个你不会出错的。
关联：
http://kr.github.com/beanstalkd/
Beanstalkd just rocks- Tubes function as pub-sub and can just work like a charm on any cloud vendor. 3-7 minutes to setup. Blazingly fast since uses memcache like queue.
You can write workers in any language you chose from. You cannot go wrong with this one.
Link:
http://kr.github.com/beanstalkd/