4 ms·
I completely avoided the need for maintaining an additional dependency (ElasticSearch) simply by taking advantage of fulltext search in Postgres. This did invol
by pmarreck 3y ago
I completely avoided the need for maintaining an additional dependency (ElasticSearch) simply by taking advantage of fulltext search in Postgres. This did involve some writing of triggers and stored procedure code (which was generated by server-side code, but anyway), which is technically application logic.
There are no perfect solutions in engineering, only tradeoffs.
- JohnBooty 3y agoI love this! There are definitely cons to moving functionality to Postgres, but avoiding an additional dependency can be a massive pro.