Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/distributed-search

@228d57d
Run it yourself

This skill should be used when the user designs a "search system", needs "full-text search", asks about an "inverted index", "Elasticsearch / OpenSearch", "relevance ranking" (TF-IDF/BM25), "search autocomplete / typeahead", an "indexing pipeline", or "faceted search". It gives the crawl/index/search architecture, index sharding and replication, ranking, and near-real-time indexing. Use it whenever users must query text by relevance rather than fetch rows by key, even if they don't say "search engine".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/distributed-search

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersgcp.md

≈491 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Distributed search — GCP

Service mapping

  • Vertex AI Search (formerly Enterprise Search / Discovery Engine) — managed, Google-quality search and recommendations over your data; handles indexing, ranking, and semantic/keyword retrieval with little tuning. Use when you want a high-quality search experience without operating an engine.
  • Self-managed OpenSearch/Elasticsearch on GCE/GKE — when you need full engine control, custom analyzers/shard tuning, or cross-cloud portability; the generic recipe applies. (GCP has no managed Elasticsearch-API service of its own; Elastic Cloud on GCP is a third-party option.)
  • AlloyDB / Cloud SQL full-text — built-in DB full-text for small corpora where a separate search system isn't warranted (→ data-storage).

When to pick which

Vertex AI Search for a managed, relevance-strong experience with minimal ops and built-in semantic ranking; self-managed OpenSearch when you need explicit shard/replica/analyzer control or portability; DB full-text when the corpus is small enough not to need a cluster (YAGNI).

Limits / things that bite (verify against current docs)

  • Vertex AI Search abstracts the index — you trade low-level shard/analyzer control for managed quality; verify it supports your filter/facet/freshness needs before committing.
  • Quotas on data stores, documents, and QPS per project apply.
  • Self-managed clusters carry the generic operational burden (heap, merges, shard sizing) plus regional/VPC placement affecting latency.

Pitfalls

  • Assuming a drop-in Elasticsearch-API managed service exists natively — it doesn't; either use Vertex AI Search's model or self-manage / Elastic Cloud.
  • Adopting Vertex AI Search then needing custom analyzers/scoring it doesn't expose.
  • Treating any of these as a source of truth rather than a reindexable derived copy.
  • Lock-in: Vertex AI Search data stores and config don't port to other clouds.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    This skill is a technical architecture guide for designing distributed search systems and contains no security risks. It consists entirely of documentation and design patterns.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/distributed-search