3 ms·
So Amazon forking ES is then ensuring that if Elastic dies, ElasticSearch doesn’t go away, right? Part of the problem here really is that if I am using AWS for
by IgorPartola 6y ago
So Amazon forking ES is then ensuring that if Elastic dies, ElasticSearch doesn’t go away, right? Part of the problem here really is that if I am using AWS for the rest of my stack, why would I run my search elsewhere, introducing latency, etc? Elastic’s opportunity was to approach AWS and try to get bought. But their business model really isn’t as good as it seems.
- MoOmer 6y agoElastic's Cloud offering runs in the major cloud providers [0]. https://www.elastic.co/subscriptions/cloud https://www.elastic.co/subscriptions/cloud
- IgorPartola 6y agoIs it better than AWS’s implementation?
- patmorgan23 6y agoAnd/or cost competitive.
- theamk 6y agoLooking at a single machine (i3.large, 15GB ram, 470GB SD): Raw EC2 costs: $0.156/hr or $112/month AWS Elasticsearch: $0.25/hr or $180/month Elastic's Elasticsearch: $0.3375/hr or $243/month (price stays about the same for 1, 2 or 3 nodes)
- IgorPartola 6y agoSo if we assume the level of service is not much better, AWS is the more prudent choice, no? So trademark issues aside, AWS does ES better than Elastic?
- budlightvirus 6y agoTo me that would depend on whether AWS Elasticsearch is actually profitable at that price point, or whether they are running at a loss to grab market share.
- IgorPartola 6y agoThe quality of the service you get depends on if AWS makes a profit? Also, do you think they make a profit on the bare EC2 instance? If so, why do you think that running a few management scripts that manage ES running on it would add up to more than $0.094/hour?