Windows Azure 存储（Blob、表、队列）是否针对 Windows Azure 角色的访问进行了优化？
我目前正在考虑在 Windows Azure 上托管 ElasticSearch 实现。加载应用程序并在 Java 下运行它并不那么困难。
目前，仅限 ElasticSearch在云存储方面支持亚马逊的S3。
因此，我请求在 ElasticSearch 中添加对 Azure Blob 存储的支持。
在我发出请求后，我突然想到，虽然我可以在 Azure 中托管 ElasticSearch，但我可以创建一个 Amazon S3 帐户然后让在 Azure 中运行的实例连接到 S3 帐户进行存储。
然而，我确实担心两者之间的速度。虽然我确信 Azure 存储和 Amazon S3 都针对非常快的速度进行了优化，但我有一种挥之不去的感觉，即从各自的计算集群访问时，存储系统确实得到了优化。
也就是说，有这方面的确切信息吗？这是有道理的，但我正在寻找具体的确认或否认。
I'm currently looking at Windows Azure to host an ElasticSearch implementation. Loading the application and running it under Java is not that difficult.
Currently, ElasticSearch only supports Amazon's S3 when it comes to cloud storage.
As a result, I've made a request to add support for Azure Blob Storage in ElasticSearch.
Right after I made the request, it occured to me that while I can host ElasticSearch in Azure, I can create an Amazon S3 account and then have the instance running in Azure connect to the S3 account for storage.
However, I do have concerns about the speed between the two. While I am sure both Azure Storage and Amazon's S3 are both optimized for really fast speeds, I have a nagging feeling that storage systems are really optimized when accessed from their respective computing clusters.
That said, is there any definitive information on this? It makes sense, but I'm looking for specific confirmation or denial.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这并不是针对 Azure 角色优化 Azure 存储 API 的问题，而只是物理共置和网络距离/跳数的问题。您可以（并且应该）指定您的 Azure 存储服务与将使用该存储服务的 Azure 角色位于同一数据中心。
您可以预期同一数据中心内的 Azure 角色和 Azure 存储之间的网络带宽最大，延迟最低。当您的 Azure 角色连接到其自己的数据中心之外的任何内容（无论是另一个数据中心中的 Azure 存储，还是另一个数据中心中的 Amazon S3 存储）时，带宽会更低，延迟会更高。
除了性能之外，还请记住，您需要为服务进出 Azure 数据中心的所有数据流量付费。让您的 Azure 角色访问 Amazon S3 或另一个 Azure 数据中心中的数据将会占用您的带宽配额，而访问同一数据中心内的 Azure 存储则不会产生任何费用，无论您的角色和您的角色之间使用了多少流量。 Azure 存储。
It's not so much a matter of optimization of the Azure storage API for Azure Roles, but simply a matter of physical co-location and network distance / number of hops. You can (and should) specify that your Azure storage service resides in the same data center as the Azure roles that will be using that storage service.
You can expect network bandwidth to be greatest and latency to be lowest between an Azure role and an Azure storage residing in the same data center. Bandwidth will be lower and latency higher when your Azure role connects to anything outside of its own data center - be that Azure storage in another data center, or Amazon S3 storage in another data center.
Besides performance, also keep in mind that you pay for all data traffic in and out of the Azure data center for your services. Having your Azure role accessing data on Amazon S3 or in another Azure data center will take a bite out of your bandwidth quota, whereas accessing Azure storage within the same data center costs you nothing, no matter how much traffic you use between your role and your Azure storage.