Inverted indexes are almost always eventually consistent, and easy to integrate in a distributed context.
- Store documents into R2 or Durable Objects or KV or (Cloudflare future storage).
- Create inverted index files (similar to Lucene)
- Cache the inverted index files at the edge. Cloudflare’s bread and butter.
- Run query execution nodes at the edge. Deal with the occasional cache miss by proxying to a different region.
- Its impossible to deal with relevance or ranking for that many different use cases. Let the clients control every aspect of relevancy and ranking, e.g. Similar to the flexibility of ElasticSearch.
Full text search, please :)
Inverted indexes are almost always eventually consistent, and easy to integrate in a distributed context.
- Store documents into R2 or Durable Objects or KV or (Cloudflare future storage).
- Create inverted index files (similar to Lucene)
- Cache the inverted index files at the edge. Cloudflare’s bread and butter.
- Run query execution nodes at the edge. Deal with the occasional cache miss by proxying to a different region.
- Its impossible to deal with relevance or ranking for that many different use cases. Let the clients control every aspect of relevancy and ranking, e.g. Similar to the flexibility of ElasticSearch.