3 ms·
As someone who has to use Elasticsearch as an only data store, yes.
by psv1 7y ago
As someone who has to use Elasticsearch as an only data store, yes.
- noobiemcfoob 7y ago>use Elasticsearch Found your problem.
- licnep 7y agoCan you elaborate on which issue(s) you encountered? We are considering Elasticsearch at the moment for document storage and search, versus postgres.
- qohen 7y agoFYI, you might want to check out ZomboDB[0], which integrates Postgres and ElasticSearch. It's open source[1] and, fwiw, the developer was helpful when I pinged him with some questions a while back (and is available for consulting services). From the project's github page[1]: ZomboDB brings powerful text-search and analytics features to Postgres by using Elasticsearch as an index type. Its comprehensive query language and SQL functions enable new and creative ways to query your relational data. From a technical perspective, ZomboDB is a 100% native Postgres extension that implements Postgres' Index Access Method API. As a native Postgres index type, ZomboDB allows you to CREATE INDEX ... USING zombodb on your existing Postgres tables. At that point, ZomboDB takes over and fully manages the remote Elasticsearch index and guarantees transactionally-correct text-search query results. [0] https://www.zombodb.com/ https://www.zombodb.com/ [1] https://github.com/zombodb/zombodb https://github.com/zombodb/zombodb
- matwood 7y agoI typically keep search indexing separate from document storage and delivery. That way I can design each independently to do what they do best. Something like postgres can do both, but I would still logically separate the problems so I can move to better solutions when they arise.
- mahkeiro 7y agoCome on now even ES has an SQL interface.