Hacker News new | ask | show | jobs
by manuelabeledo 1293 days ago
A couple years ago, I was evaluating moving our ES clusters to the cloud. I got quotes from both Elastic and AWS.

How much more Elastic wanted than AWS, didn't make sense, not even factoring support and hosting. It was like almost twice as much.

Morally, I get why I should have gone with Elastic. Too bad businesses aren't about morals.

3 comments

In all fairness, there is more than just cost when choosing a provider. Elastic has had higher uptime than the AWS alternative. I had to switch off AWS Elasticsearch hosting because it kept going down.
If your use case is faster search - ES cloud is way more efficient/performs better than AWS. They manage their cloud stack pretty well. I hate those `amazon.internal` stack trace in thread stack ( when you try to troubleshoot something in prod) as you have no access to code to see what it even does.
True, last I check the gap wasn't too big anymore, I think even comparable for certain machine configurations.

One thing is that the "mainstream" ELK develops at a much faster speed than the OpenSearch fork, and a lot of the nice features in new versions are nowhere to be seen in OpenSearch.