When we reach for it
Product and document search where relevance is the feature, and log analytics at a volume that has outgrown grep.
Elasticsearch engineering
A search and analytics engine for the queries a relational database is bad at: relevance ranking, fuzzy matching and aggregation across large document sets.
When we would argue against it
It is not a system of record and should never be the only copy of anything. Running a cluster is real operational work, and PostgreSQL’s full-text search is enough for a surprising number of the cases it gets bought for.
What it looks like in delivery
Indexed from the system of record so it can always be rebuilt, with relevance tuned against queries real users actually typed rather than the examples in the ticket.
Where this appears on the site
Nothing on this site names it yet
We work in Elasticsearch, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.
Working in Elasticsearch?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.