We use Amazon S3 and CDN. Our app runs on Heroku. We are thinking of using a DBaaS like RDS or Xeround.
我们使用Amazon S3和CDN。我们的应用程序在Heroku上运行。我们正在考虑使用DBaaS，如RDS或Xeround。
Because we are already using S3 and CDN from Amazon, should we use RDS? Since all technologies are running on the same host (Amazon), will there be any performance gain, rather than using something that is of third-party (Xeround)?
因为我们已经在使用来自Amazon的S3和CDN，我们应该使用RDS吗?由于所有的技术都在同一台主机上运行(Amazon)，是否会有任何性能增益，而不是使用第三方的(Xeround)?
Or it shouldn't matter?
或者它不重要吗?
4 个解决方案
#1
7
I work for Xeround and wanted to outline the key differentiators between our database service and Amazon's RDS.
我在Xeround工作，希望概述一下我们的数据库服务和亚马逊的RDS之间的主要区别。
Contrary to common perception, Amazon RDS is not a truly elastic cloud database service, but an implementation of MySQL on EC2. Xeround on the other hand is a native cloud database that's extremely easy to use- taking the pain out of scaling and maintaining high-availability for your MySQL in the cloud.
与普遍的看法相反，Amazon RDS并不是真正的弹性云数据库服务，而是EC2上的MySQL实现。另一方面，Xeround是一个非常容易使用的本地云数据库，这让您摆脱了在云中维护MySQL高可用性的痛苦。
Key Differentiators Between Xeround and Amazon RDS:
Xeround和亚马逊RDS的主要区别:
1) Xeround supports unlimited Auto-Scaling up/out & down/in with no service downtime or any code changes or architectural changes to your application. This industry-first capability is in contrast to Amazon's manual scaling with down time. We automatically add nodes or storage to your DB when the application demands it, and shrink it back down when the database is underutilized- so you only pay for what you use. you don't need to figure out what's your current usage and what growth you're planning for- the DB resources would automatically adjust to meet your needs at any given time.
1) Xeround支持无限制的自动扩展/扩展/扩展/向下扩展/进入，没有服务停机时间，也没有对应用程序进行任何代码更改或架构更改。这个行业第一的能力与亚马逊的随时间的手工扩展形成了对比。当应用程序需要时，我们会自动将节点或存储添加到您的DB中，当数据库未得到充分利用时，我们会将其缩小，因此您只需要为使用的内容付费。您不需要知道您当前的使用情况和您计划的增长情况——DB资源会自动调整以满足您的需求。
2) Xeround never fails – even when Amazon’s instance fails. (BTW- in the latest EC2 outage- when RDS customers had as much as 14 hours of downtime, Xeround's databases on the same data centers continued to work as if nothing had happened- you can read more about the outage on our blog).
2) Xeround永远不会失败——即使亚马逊的实例失败了。(顺便说一下，在最新的EC2故障中，当RDS的客户有多达14小时的停机时间时，Xeround在相同数据中心上的数据库继续工作，就好像什么都没有发生过一样——你可以在我们的博客上看到更多关于宕机的信息)。
Xeround offers a highly available, self-healing, database, with no downtime guarantee. Most importantly- you don't need to be bothered with replicas, distribution etc. to ensure HA- it's built-in to the service.
Xeround提供了一个高度可用的、自愈的数据库，没有停机保证。最重要的是——您不需要为副本、发行版等而烦恼，以确保HA——它是服务内置的。
3) Xeround offers TRUE pay-per-use model, vs. RDS which requires you to commit to an instance-size with preset processing power and storage. This often results in over subscription and over-paying as you prepare for a peak. We are finalizing our pricing these days- it'll be based on two metrics: data size and data transfer - so that your costs are tightly linked to the performance and demand of your application, with auto-scaling, availability SLAs, scheduled backup and 24/7/365 support all included.
3) Xeround提供了真正的按次付费模式，而RDS要求您提交一个实例大小，并具有预先设置的处理能力和存储能力。这通常会导致超额认购和超额支付，当你准备高峰。我们现在正在确定我们的定价——它将基于两个指标:数据大小和数据传输——因此您的成本与应用程序的性能和需求紧密相关，包括自动伸缩、可用性sla、计划备份和24/7/365支持。
You can see the detailed comparison to Amazon RDS, as well as our RDS performance benchmark comparison showing that Xeround performs much better than RDS particularly as the number of concurrent users grows (we'll soon publish an update to the benchmark with even better results).
您可以看到与Amazon RDS的详细比较，以及我们的RDS性能基准比较，显示Xeround的性能比RDS要好得多，尤其是并发用户数量增加时(我们将很快发布对基准的更新，获得更好的结果)。
Regarding latency: note that Xeround is deployed on Amazon EC2 in US-East and in EU-West- so if you app runs on the same datacenter latency should be minimal.
关于延迟:请注意，Xeround部署在US-East和EU-West的Amazon EC2上——因此，如果应用程序运行在相同的数据中心上，延迟应该是最小的。
In addition, we're also have an Heroku add-on that you can easily add to your app (DB would also be deployed on EC2-US-East).
此外，我们还有一个Heroku附加组件，您可以轻松地添加到您的应用程序中(DB也将部署到EC2-US-East上)。
hope this helps.
希望这个有帮助。
#2
9
Be aware that Xeround DOES NOT support foreign Key constraints (and they don't make it clear). So if your application depends on this database feature to keep you data consistent, don't use Xeround.
请注意Xeround不支持外键约束(它们也不清楚)。因此，如果您的应用程序依赖于这个数据库特性来保持数据的一致性，那么就不要使用Xeround。
http://xeround.com/developers/release-notes/
http://xeround.com/developers/release-notes/
"Foreign Key constraints are supported but not enforced"
“支持外键约束，但不强制执行”
#3
1
This is a hard topic. I faced the very same question 2 months ago.
这是一个很难的话题。两个月前我遇到了同样的问题。
- Amazon RDS
- Amazon RDS
Pros: it's Amazon thus well known, mature and reliable
优点:亚马逊是众所周知、成熟和可靠的。
Cons: They faced many downtimes at the beginning of the year + some people complain about the slowness of the service (claiming it's faster to run a MySql db on EC2)
缺点:他们在年初的时候遇到了很多的困难+一些人抱怨服务的缓慢(声称在EC2上运行MySql db更快)
- Xeround
- Xeround
Pros: I still don't know but it's good looking :)
优点:我还是不知道，但是看起来不错。
Cons: Still in early stage, no price displayed (Am I missing something?)
缺点:仍处于初期阶段，没有显示价格(我是否遗漏了什么?)
#4
0
Since Xeround announced today that they are pulling the plug on their DBaaS, the choice is now more obvious
自从Xeround在今天宣布退出DBaaS以来，现在的选择就更加明显了
http://gigaom.com/2013/05/01/xeround-pulls-the-plug-on-free-cloud-database-option/
http://gigaom.com/2013/05/01/xeround-pulls-the-plug-on-free-cloud-database-option/
#1
7
I work for Xeround and wanted to outline the key differentiators between our database service and Amazon's RDS.
我在Xeround工作，希望概述一下我们的数据库服务和亚马逊的RDS之间的主要区别。
Contrary to common perception, Amazon RDS is not a truly elastic cloud database service, but an implementation of MySQL on EC2. Xeround on the other hand is a native cloud database that's extremely easy to use- taking the pain out of scaling and maintaining high-availability for your MySQL in the cloud.
与普遍的看法相反，Amazon RDS并不是真正的弹性云数据库服务，而是EC2上的MySQL实现。另一方面，Xeround是一个非常容易使用的本地云数据库，这让您摆脱了在云中维护MySQL高可用性的痛苦。
Key Differentiators Between Xeround and Amazon RDS:
Xeround和亚马逊RDS的主要区别:
1) Xeround supports unlimited Auto-Scaling up/out & down/in with no service downtime or any code changes or architectural changes to your application. This industry-first capability is in contrast to Amazon's manual scaling with down time. We automatically add nodes or storage to your DB when the application demands it, and shrink it back down when the database is underutilized- so you only pay for what you use. you don't need to figure out what's your current usage and what growth you're planning for- the DB resources would automatically adjust to meet your needs at any given time.
1) Xeround支持无限制的自动扩展/扩展/扩展/向下扩展/进入，没有服务停机时间，也没有对应用程序进行任何代码更改或架构更改。这个行业第一的能力与亚马逊的随时间的手工扩展形成了对比。当应用程序需要时，我们会自动将节点或存储添加到您的DB中，当数据库未得到充分利用时，我们会将其缩小，因此您只需要为使用的内容付费。您不需要知道您当前的使用情况和您计划的增长情况——DB资源会自动调整以满足您的需求。
2) Xeround never fails – even when Amazon’s instance fails. (BTW- in the latest EC2 outage- when RDS customers had as much as 14 hours of downtime, Xeround's databases on the same data centers continued to work as if nothing had happened- you can read more about the outage on our blog).
2) Xeround永远不会失败——即使亚马逊的实例失败了。(顺便说一下，在最新的EC2故障中，当RDS的客户有多达14小时的停机时间时，Xeround在相同数据中心上的数据库继续工作，就好像什么都没有发生过一样——你可以在我们的博客上看到更多关于宕机的信息)。
Xeround offers a highly available, self-healing, database, with no downtime guarantee. Most importantly- you don't need to be bothered with replicas, distribution etc. to ensure HA- it's built-in to the service.
Xeround提供了一个高度可用的、自愈的数据库，没有停机保证。最重要的是——您不需要为副本、发行版等而烦恼，以确保HA——它是服务内置的。
3) Xeround offers TRUE pay-per-use model, vs. RDS which requires you to commit to an instance-size with preset processing power and storage. This often results in over subscription and over-paying as you prepare for a peak. We are finalizing our pricing these days- it'll be based on two metrics: data size and data transfer - so that your costs are tightly linked to the performance and demand of your application, with auto-scaling, availability SLAs, scheduled backup and 24/7/365 support all included.
3) Xeround提供了真正的按次付费模式，而RDS要求您提交一个实例大小，并具有预先设置的处理能力和存储能力。这通常会导致超额认购和超额支付，当你准备高峰。我们现在正在确定我们的定价——它将基于两个指标:数据大小和数据传输——因此您的成本与应用程序的性能和需求紧密相关，包括自动伸缩、可用性sla、计划备份和24/7/365支持。
You can see the detailed comparison to Amazon RDS, as well as our RDS performance benchmark comparison showing that Xeround performs much better than RDS particularly as the number of concurrent users grows (we'll soon publish an update to the benchmark with even better results).
您可以看到与Amazon RDS的详细比较，以及我们的RDS性能基准比较，显示Xeround的性能比RDS要好得多，尤其是并发用户数量增加时(我们将很快发布对基准的更新，获得更好的结果)。
Regarding latency: note that Xeround is deployed on Amazon EC2 in US-East and in EU-West- so if you app runs on the same datacenter latency should be minimal.
关于延迟:请注意，Xeround部署在US-East和EU-West的Amazon EC2上——因此，如果应用程序运行在相同的数据中心上，延迟应该是最小的。
In addition, we're also have an Heroku add-on that you can easily add to your app (DB would also be deployed on EC2-US-East).
此外，我们还有一个Heroku附加组件，您可以轻松地添加到您的应用程序中(DB也将部署到EC2-US-East上)。
hope this helps.
希望这个有帮助。
#2
9
Be aware that Xeround DOES NOT support foreign Key constraints (and they don't make it clear). So if your application depends on this database feature to keep you data consistent, don't use Xeround.
请注意Xeround不支持外键约束(它们也不清楚)。因此，如果您的应用程序依赖于这个数据库特性来保持数据的一致性，那么就不要使用Xeround。
http://xeround.com/developers/release-notes/
http://xeround.com/developers/release-notes/
"Foreign Key constraints are supported but not enforced"
“支持外键约束，但不强制执行”
#3
1
This is a hard topic. I faced the very same question 2 months ago.
这是一个很难的话题。两个月前我遇到了同样的问题。
- Amazon RDS
- Amazon RDS
Pros: it's Amazon thus well known, mature and reliable
优点:亚马逊是众所周知、成熟和可靠的。
Cons: They faced many downtimes at the beginning of the year + some people complain about the slowness of the service (claiming it's faster to run a MySql db on EC2)
缺点:他们在年初的时候遇到了很多的困难+一些人抱怨服务的缓慢(声称在EC2上运行MySql db更快)
- Xeround
- Xeround
Pros: I still don't know but it's good looking :)
优点:我还是不知道，但是看起来不错。
Cons: Still in early stage, no price displayed (Am I missing something?)
缺点:仍处于初期阶段，没有显示价格(我是否遗漏了什么?)
#4
0
Since Xeround announced today that they are pulling the plug on their DBaaS, the choice is now more obvious
自从Xeround在今天宣布退出DBaaS以来，现在的选择就更加明显了
http://gigaom.com/2013/05/01/xeround-pulls-the-plug-on-free-cloud-database-option/
http://gigaom.com/2013/05/01/xeround-pulls-the-plug-on-free-cloud-database-option/