Managed elasticsearch is pretty expensive, and adds another service to interact with.
Postgres full text search (FTS) is pretty good, and we basically always already have a postgres database.
Django has good support for FTS, and we've used in the the past, but in our projects this has meant building custom search interfaces. It would be be able to use Haystack and have postgres be a backend for haystack.
Proposal
A public repo of a hastack backend that is installable from github
A migration document from using elasticsearch as the backend to using postgres
Here's an example of a third-party haystack backend that is a good bit more complicated than we need, but should give us some guidance on organizing the code and entry points.
Background
Managed elasticsearch is pretty expensive, and adds another service to interact with.
Postgres full text search (FTS) is pretty good, and we basically always already have a postgres database.
Django has good support for FTS, and we've used in the the past, but in our projects this has meant building custom search interfaces. It would be be able to use Haystack and have postgres be a backend for haystack.
Proposal
Notes on implementation
Haystack's SimpleBackend would be the starting point. Like that model, we would not implement the methods that are used to create the index, because we would handle those on the models, with GeneratedFields and SearchVectorFields.
SimpleBackend is very simple, and we would want to implement at least faceting, and maybe also "more like this".
Here are some notes on an implementation of facetting with postgres FTS that could be useful.
Here's an example of a third-party haystack backend that is a good bit more complicated than we need, but should give us some guidance on organizing the code and entry points.