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.

referencesprovidersazure.md

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

Distributed search — Azure

Service mapping

  • Azure AI Search (formerly Cognitive Search) — managed search service: inverted-index full-text (BM25), facets, suggesters/autocomplete, indexers that pull from data sources (Blob, Cosmos DB, SQL), and optional vector/semantic ranking. The default managed search on Azure; it abstracts shards behind replicas (query throughput/HA) and partitions (index size/capacity).
  • Self-managed OpenSearch/Elasticsearch on VMs/AKS — when you need full engine control or portability; then the generic recipe applies.

When to pick which

AI Search when you want a managed, batteries-included search with built-in indexers and suggesters and don't want to operate a cluster; self-managed OpenSearch when you need low-level shard/analyzer control or cross-cloud portability.

Limits / things that bite (verify against current docs)

  • Capacity is set by replicas × partitions (search units); both are bounded per tier and the tier caps total index size and doc count — pick the tier from your corpus bytes, and re-tiering can mean a rebuild.
  • Indexers (the pull pipeline) have batch-size and run-frequency limits; large or fast-changing corpora can lag — monitor indexer freshness.
  • Per-tier caps on indexes, fields, and queries-per-second.

Pitfalls

  • Under-provisioning partitions for a growing corpus, then hitting a tier change.
  • Relying solely on built-in indexers for near-real-time freshness without a push path / durable buffer in front (→ messaging-streaming).
  • Treating it as a primary store rather than a reindexable derived copy.
  • Lock-in: skillsets, indexers, and semantic ranking configs are Azure-specific.

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