5 ms·

It definitely seems like it's gotten more robust since the 0.9.x/1.x/2.x days. And a lot of stuff that had to be done externally is starting to be baked into t

by chrsig 4y ago

It definitely seems like it's gotten more robust since the 0.9.x/1.x/2.x days. And a lot of stuff that had to be done externally is starting to be baked into the service itself (rolling over indices, rolling up based on a query) I'm a bit cautious using 8.x, because opensearch forked at 7.x. I don't really have any desire to keep track of any divergences between the two :-/ It's really unfortunate that there's so much bad blood between elastic and aws.

adql 4y ago
Ye back then it seemed like every month or two they had some bug in their own clustering stuff that they wrote from scratch instead of going with tested ones like raft or paxos
- chrsig 4y ago
  Yeah, I'd be really curious how it fairs on jespen now. Back then it did...poorly https://aphyr.com/posts/323-jepsen-elasticsearch-1-5-0 https://aphyr.com/posts/323-jepsen-elasticsearch-1-5-0
  - karlney 4y ago
    This is a good resource for the up to date resilience status in Elasticsearch https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html https://www.elastic.co/guide/en/elasticsearch/resiliency/cur... They have gotten A LOT better since the 1.x days
olavgg 4y ago
What do people go for these days? I am working at a startup, and I need to pick either OpenSearch or Elasticsearch. So far I've concluded with that Solr is not that good in a cluster setup. The last option is using FTS in PostgreSQL, which is by far the easiest solution and I can always "upgrade" later.
- vosper 4y ago
  I’m in a similar boat, and my gut says to go with ES over OpenSearch. I’ve no idea how committed Amazon are to OpenSearch, and no idea of the quality or size of the team working on it. For Elastic ES is their core product. At AWS OpenSearch is one minor product amongst many.
- flockonus 4y ago
  At this point the fork is recent enough that I haven't noted much of a split, altho i'd agree it tends to compound. Might want to look at the licenses and support to where you plan hosting it.
- caseydm 4y ago
  Our startup uses managed elasticsearch through elastic. We're a very small team so support/consulting advice is important to us and they are good at that.
- ddorian43 4y ago
  Check out vespa.ai
- clone1018 4y ago
  I've had really poor experiences so far from Elastic.co. Their core ElasticSearch offering seems to be on the backburner while they focus on "App Search" and other unrelated products like their APM offering. This leads to pretty sub-par knowledge and support for the ElasticSearch product. Even simple things like paginating results is an unknown, and you really have to pay deep into their ecosystem to get real implementation support. Oddly enough too, due to the way their cloud hosting infrastructure works it seems they double dip into bandwidth pricing that should otherwise be free (eg AWS => AWS). It's also treated less as a "Software" as a service, and more a "platform" as a service, so you are left ultimately with the responsibility of managing, maintaining, and updating your Elastic cluster, without any ability to SSH into the servers its running on. Then there's the unprofessionalism of laying off your account manager during a client call, or telling your client that you're sorry their ElasticSearch infrastructure is down, but they can't really help you unless you're on their "Sapphire Extreme Plan" [sic]... Even if OpenSearch is just a cog in Amazon's offering, at least it's of a known quantity.

by chrsig 4y ago

adql 4y ago

Ye back then it seemed like every month or two they had some bug in their own clustering stuff that they wrote from scratch instead of going with tested ones like raft or paxos

chrsig 4y ago
Yeah, I'd be really curious how it fairs on jespen now. Back then it did...poorly https://aphyr.com/posts/323-jepsen-elasticsearch-1-5-0 https://aphyr.com/posts/323-jepsen-elasticsearch-1-5-0
- karlney 4y ago
  This is a good resource for the up to date resilience status in Elasticsearch https://www.elastic.co/guide/en/elasticsearch/resiliency/current/index.html https://www.elastic.co/guide/en/elasticsearch/resiliency/cur... They have gotten A LOT better since the 1.x days

olavgg 4y ago

What do people go for these days? I am working at a startup, and I need to pick either OpenSearch or Elasticsearch. So far I've concluded with that Solr is not that good in a cluster setup. The last option is using FTS in PostgreSQL, which is by far the easiest solution and I can always "upgrade" later.

vosper 4y ago
I’m in a similar boat, and my gut says to go with ES over OpenSearch. I’ve no idea how committed Amazon are to OpenSearch, and no idea of the quality or size of the team working on it. For Elastic ES is their core product. At AWS OpenSearch is one minor product amongst many.
flockonus 4y ago
At this point the fork is recent enough that I haven't noted much of a split, altho i'd agree it tends to compound. Might want to look at the licenses and support to where you plan hosting it.
caseydm 4y ago
Our startup uses managed elasticsearch through elastic. We're a very small team so support/consulting advice is important to us and they are good at that.
ddorian43 4y ago
Check out vespa.ai
clone1018 4y ago
I've had really poor experiences so far from Elastic.co. Their core ElasticSearch offering seems to be on the backburner while they focus on "App Search" and other unrelated products like their APM offering. This leads to pretty sub-par knowledge and support for the ElasticSearch product. Even simple things like paginating results is an unknown, and you really have to pay deep into their ecosystem to get real implementation support. Oddly enough too, due to the way their cloud hosting infrastructure works it seems they double dip into bandwidth pricing that should otherwise be free (eg AWS => AWS). It's also treated less as a "Software" as a service, and more a "platform" as a service, so you are left ultimately with the responsibility of managing, maintaining, and updating your Elastic cluster, without any ability to SSH into the servers its running on. Then there's the unprofessionalism of laying off your account manager during a client call, or telling your client that you're sorry their ElasticSearch infrastructure is down, but they can't really help you unless you're on their "Sapphire Extreme Plan" [sic]... Even if OpenSearch is just a cog in Amazon's offering, at least it's of a known quantity.