Closed SamDepardieu closed 4 years ago
At the moment, Reach is using Elasticsearch as its backend database.
Elasticsearch is great to perform search operation in an optimised way, leading to better search speed into the huge number of publication we store.
This speed comes with a loss of customisation in our requests, that we currently want to get back to implement the new search features.
PostgreSQL offers good search speed and a better customisation level in the queries.
search_api
Can this be closed now @SamDepardieu ?
Sadly, not yet... I'm still fixing some stuff in there
Rationale
At the moment, Reach is using Elasticsearch as its backend database.
Elasticsearch is great to perform search operation in an optimised way, leading to better search speed into the huge number of publication we store.
This speed comes with a loss of customisation in our requests, that we currently want to get back to implement the new search features.
PostgreSQL offers good search speed and a better customisation level in the queries.
Expected outcomes
Success criteria
search_api
relies on a postrges backend