4 ms·

> To be an effective alternative to Elasticsearch we needed to support high ingest workloads in real time. Why not just use OpenSearch or ElasticSearch? The to

> To be an effective alternative to Elasticsearch we needed to support high ingest workloads in real time. Why not just use OpenSearch or ElasticSearch? The tool is already in the inventory; why use a screwdriver when a chisel is needed and available? This is another one of those “when you have a hammer, everything looks like your thumb” stories.

AtlasBarfed 1y ago
Why not the Cassandra based elastics if you need ingest?
izietto 1y ago
Because it's a whole another architectural component for data that is already there, in a tool that is made just for that lacking just of `SELECT full_text_search('kitty pictures');`
cheema33 1y ago
> Why not just use OpenSearch or ElasticSearch? There is a cost associated with adopting and integrating another tool like ElasticSearch. For some orgs, the ROI might not be there. And if their existing database provide some additional capabilities in this space, that might be preferrable. > This is another one of those “when you have a hammer, everything looks like your thumb” stories. Are you referring to people who think that every reporting problem must be solved by a dedicated OLAP database?
bastawhiz 1y ago
Running elasticsearch is a miserable experience. If you can run one tool that you already have with slightly more effort, amazing. And you never need to think about rebuilding indexes or tuning the garbage collector or planning an ES major version migration.
iw2rmb 1y ago
Because you don’t need to sync and you have ACID with joins.
- otterley 1y ago
  Is there a whole business to be had with those advantages alone? I’m curious as to who the target market is.
  - levkk 1y ago
    My last big co, we had a team of 10 who's entire job was to sync data from Postgres into Elastic. It would take weeks and fallover regularly due to traffic. If we could have a DB that could do search and be a store of record, it would be amazing.
    - mathewpregasen 1y ago
      Yeah, in general, I think a lot of businesses would love to skip ETL pipelines if possible / consolidate data. Postgres is a very much a neutral database to extend upon, maybe a wild analogy but it's the canola oil of databases
      - deleted 1y ago
        [deleted]
      - strbean 1y ago
        Total tangent, but I think "Canola is a neutral oil" is a lie. It's got the most distinctive (and in my opinion, bad) flavor of the common cooking oils.
        retakeming 1y ago
        What would you say is the most neutral oil then?
        ahartmetz 1y ago
        Sunflower oil? It seems to very reliably taste like nothing.
sandeepkd 1y ago
There can be multiple reasons, one that I can think of right away would be to keep the stack as simple as possible until you can. Realistically speaking most of the companies do not operate at the scale where they would need the specialized tools.

AtlasBarfed 1y ago

Why not the Cassandra based elastics if you need ingest?

izietto 1y ago

Because it's a whole another architectural component for data that is already there, in a tool that is made just for that lacking just of `SELECT full_text_search('kitty pictures');`

cheema33 1y ago

> Why not just use OpenSearch or ElasticSearch? There is a cost associated with adopting and integrating another tool like ElasticSearch. For some orgs, the ROI might not be there. And if their existing database provide some additional capabilities in this space, that might be preferrable. > This is another one of those “when you have a hammer, everything looks like your thumb” stories. Are you referring to people who think that every reporting problem must be solved by a dedicated OLAP database?

bastawhiz 1y ago

Running elasticsearch is a miserable experience. If you can run one tool that you already have with slightly more effort, amazing. And you never need to think about rebuilding indexes or tuning the garbage collector or planning an ES major version migration.

iw2rmb 1y ago

Because you don’t need to sync and you have ACID with joins.

otterley 1y ago
Is there a whole business to be had with those advantages alone? I’m curious as to who the target market is.
- levkk 1y ago
  My last big co, we had a team of 10 who's entire job was to sync data from Postgres into Elastic. It would take weeks and fallover regularly due to traffic. If we could have a DB that could do search and be a store of record, it would be amazing.
  - mathewpregasen 1y ago
    Yeah, in general, I think a lot of businesses would love to skip ETL pipelines if possible / consolidate data. Postgres is a very much a neutral database to extend upon, maybe a wild analogy but it's the canola oil of databases
    - deleted 1y ago
      [deleted]
    - strbean 1y ago
      Total tangent, but I think "Canola is a neutral oil" is a lie. It's got the most distinctive (and in my opinion, bad) flavor of the common cooking oils.
      - retakeming 1y ago
        What would you say is the most neutral oil then?
        ahartmetz 1y ago
        Sunflower oil? It seems to very reliably taste like nothing.

sandeepkd 1y ago

There can be multiple reasons, one that I can think of right away would be to keep the stack as simple as possible until you can. Realistically speaking most of the companies do not operate at the scale where they would need the specialized tools.