I am presently searching at Home windows Azure to host an ElasticSearch implementation. Loading the applying and running it under Java isn't so complicated.
Presently, ElasticSearch only supports Amazon's S3 if this involves cloud storage.
Consequently, I have designed a request to include support for Azure Blob Storage in ElasticSearch.
Immediately after I made the request, it happened in my experience that although I'm able to host ElasticSearch in Azure, I'm able to create an Amazon . com S3 account after which possess the instance running in Azure connect with the S3 take into account storage.
However, I actually do have concerns concerning the speed between your two. While I am certain both Azure Storage and Amazon's S3 are generally enhanced for really fast speeds, I've got a nagging feeling that storage systems are really enhanced when utilized using their particular computing groupings.
Nevertheless, can there be any definitive info on this? It seems sensible, but I am searching for specific confirmation or denial.
It's less dependent on optimisation from the Azure storage API for Azure Roles, but merely dependent on physical co-location and network distance / quantity of hops. You are able to (and really should) specify that the Azure storage service resides within the same data center because the Azure roles that'll be by using their storage service.
You may expect network bandwidth to become finest and latency to become cheapest between an Azure role as well as an Azure storage dwelling within the same data center. Bandwidth is going to be lower and latency greater whenever your Azure role connects to anything outdoors of their own data center - be that Azure storage in another data center, or Amazon . com S3 storage in another data center.
Besides performance, also bear in mind that you simply purchase all data traffic interior and exterior the Azure data center for the services. Getting your Azure role being able to access data on Amazon . com S3 or perhaps in another Azure data center will require a bite from your bandwidth quota, whereas being able to access Azure storage inside the same data center costs you nothing, regardless of how much traffic you utilize involving the role as well as your Azure storage.