Guidance on Choosing Search Solution (UI Enhancement GSoC project)

3 views
Skip to first unread message

Suprith

unread,
Mar 24, 2025, 5:05:54 AMMar 24
to chromium-gs...@chromium.org
Hi, I need guidance on whether I’m heading in the right direction.

I initially considered RediSearch since it supports all the search features needed. However, in GCP's managed version (Memorystore for Redis), Redis 7.2+ only supports vector search (AI/semantic search), which doesn’t fully align with our use case.

Would it be acceptable to use a self-managed RediSearch or ElasticSearch setup, or is it strongly recommended to stick with GCP-managed services?

I also came across Spanner’s Full-Text Search, which does provide substring search and typo correction (https://cloud.google.com/spanner/docs/full-text-search), but user search history and behavior-based search would likely require custom implementation which can be used in webstatus.dev

Before I go deeper into research, I’d like to confirm which approach makes the most sense for the project. Is there a recommended search strategy or best practice I should be following for implementing autocomplete, typo correction, and search history within GCP’s ecosystem?

Would appreciate any input on this!
Waiting for the response

Thanks!

Stephen Nusko

unread,
Mar 24, 2025, 5:30:38 AMMar 24
to chromium-gsoc-project12, Suprith
I see you already received an answer here https://issues.chromium.org/issues/398904341#comment10
Reply all
Reply to author
Forward
0 new messages