5 ms·
Is there any reason why devs choose elasticsearch to implement basic site search functionality when Postgres full text search functionality would be sufficient?
by BI440ZX 8y ago
Is there any reason why devs choose elasticsearch to implement basic site search functionality when Postgres full text search functionality would be sufficient?
Real question, because introducing another dependency like elastic over postgresql seems overkill.
- petepete 8y agoI implemented full text search in Rails with a PostgreSQL the other day and it was very straightforward. I used the pg_search gem but rolling my own query wouldn't have been too difficult. The best part is I can simply merge my search scope into the usual record-displaying eager loading Rails code and everything just works.
- ben_jones 8y agoIt's because the application developer isn't expecting, or is naive to the difficulty, of maintaining complex infrastructure for an extended period of time.
- thomasfedb 8y agoIt was definately the done thing for a while. Might just be muscle memory.
- ksec 8y agoElastic Search is many times better than Postgre in search, especially with unicode character or CJK index. Integration is easy, and it is battle tested, I would actually think not using Elastic would be the wrong approach. Something even better would be using Vesper, the search engine from Yahoo, that would definitely be overkill.