skuel-search-architecture

Unified search architecture uses a central SearchRouter to orchestrate all external requests, routing queries to domain-specific search services that query across 12 searchable domains like Activity, Curriculum, and Learning Loop. This central orchestration simplifies data discovery by aggregating results from multiple domain services into a single response.

To search within a specific domain, you use the EntityType parameter to perform targeted domain-specific searches. This narrows the query scope to a single domain, leveraging the BaseService pattern for domain search services to retrieve precise results from that specific data structure rather than querying all 12 domains at once.

Yes, you can apply advanced filtering options including graph-aware search, faceted search, and tag-based filtering to refine results. This allows you to find specific items, such as Knowledge Units that are prerequisites for active goals and also contain specific tags like 'beginner', providing highly precise search outcomes.

The best way to prioritize results is by leveraging temporal scoring patterns, which adjust item prioritization based on time-related factors. This scoring mechanism is integrated into the search architecture to ensure that recent or time-sensitive content ranks appropriately within the returned results.

Common pitfalls in search implementation often involve misconfiguring the SearchRouter orchestration or failing to correctly implement the BaseService pattern for domain search services. The architecture documentation addresses these specific issues to help developers avoid routing errors and domain query misalignment.