MarginaliaSearch/code/services-core
Viktor Lofgren a1fb92468f (refac) Remove ResultRankingParameters, QueryLimits class and use protobuf classes directly instead
This is primarily to make the code a bit easier to reason about, and will reduce the level of indirection and data copying in the search-servi->query-service->index-service communication chain.
2025-01-08 16:15:57 +01:00
..
assistant-service (search) Remove Spark and migrate to Jooby for the search service 2024-12-10 19:13:13 +01:00
control-service (refac) Remove ResultRankingParameters, QueryLimits class and use protobuf classes directly instead 2025-01-08 16:15:57 +01:00
executor-service (search) Remove Spark and migrate to Jooby for the search service 2024-12-10 19:13:13 +01:00
index-service (search) Remove Spark and migrate to Jooby for the search service 2024-12-10 19:13:13 +01:00
query-service (refac) Remove ResultRankingParameters, QueryLimits class and use protobuf classes directly instead 2025-01-08 16:15:57 +01:00
single-service-runner (chore) Remove use of deprecated STR.-style string templates 2024-11-11 18:02:28 +01:00
readme.md (refactor) Move search service into services-satellite 2023-10-09 13:40:01 +02:00

Core Services

The cores services constitute the main functionality of the search engine, relatively agnostic to the Marginalia application.

  • The index-service contains the indexes, it answers questions about which documents contain which terms.

  • The query-service Interprets queries and delegates work to index-service.

  • The control-service provides an operator's user interface, and is responsible for orchestrating the various processes of the system.

  • The assistant-service helps the search service with spelling suggestions other peripheral functionality.