qboxio

Don't forget supergiant.io which addresses the very kludgey way that Docker addresses stateful distributed apps

So, in essence that is one of the functions of the Supergiant API. We just released a few weeks ago, so AWS was our first target, but.. we are working to add support for other top cloud and on-premise providers as fast as we can. I think we are striving for OpenStack, Digital Ocean, and GCE for our next targets. If you have other targets solutions that you think we should look at, let us know :-)

Making the world a better place... with extensible and reusable nutrient delivery systems. Currently in beta (carotene).

Use the ELK Stack - Elasticsearch, Logstash, Kibana. Logstash is for ETL and data normalization. Kibana is for building cool visualizations. Elasticsearch for storing, processing, analysis, scaling and search.

Here are some resources:

Webinar: the Elk Stack in a Devops Environment http://www.elasticsearch.org/webinars/elk-stack-devops-envir...

Webinar: An Introduction to the ELK Stack http://www.elasticsearch.org/webinars/introduction-elk-stack...

Full Disclosure: Self-promotion ahead

Jono, my company, qbox.io is a provider of hosted Elasticsearch with deployments on any data center in the AWS, Rackspace, and Softlayer public clouds. You could think of us as a MongoHQ for Elasticsearch.

Yes, it will be more expensive than the infrastructure by itself, but it will also come with fast and easy Elasticsearch deployment, scaling, and support from some of the best in the business. I love Linode and AWS, but they will not know how to help you with application-specific questions.

Haters, commence hating

I think you might be attributing motives where none exist, vertex. We are a US-based company, of course subject to all the same laws. The EU datacenter was in development prior to this news breaking. The effort was solely in response to customers in the EU experiencing latency due to a transoceanic hop. The hop negates much of the benefit of using a full-text search server.

Of course, privacy expectations are set by the customer, who controls access policies.

Just to show this can work, we put together a demo called "Million Person Search". This is, as you may have guessed, a table search with a million records to demonstrate how fast ElasticSearch is when it is powered by SSD's. There is a link to Github to document it. http://qbox.io/demos

Thank you for the comment, though... that's the type of feedback we need.

Just the name and email link isn't over SSL... Once you confirm your account, then you will definitely be in https when you create an index.

We tweeted the link, herrherr... we have friends and backers, too.

If the product looks interesting, you should try the dev tier... there is no credit card required.