MarginaliaSearch/code/services-core/control-service
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
..
java/nu/marginalia/control (refac) Remove ResultRankingParameters, QueryLimits class and use protobuf classes directly instead 2025-01-08 16:15:57 +01:00
resources (export) Add export actors to precession 2024-11-26 15:07:03 +01:00
test/nu/marginalia/control (setup) Move some file-downloads from setup script to the first boot of the control node of the system 2024-11-06 15:28:20 +01:00
build.gradle (refac) Remove ResultRankingParameters, QueryLimits class and use protobuf classes directly instead 2025-01-08 16:15:57 +01:00
readme.md Clean up documentation and rename domain-links to link-graph 2024-02-28 11:40:39 +01:00

Control Service

The control service provides an operator's user interface. By default, this interface is exposed on port 8081. It does not offer any sort of access control or authentication.

The control service will itself execute tasks that affect the entire system, but delegate node-specific tasks to the corresponding to the execution subsystem.

Conceptually the application is broken into three parts:

  • Application specific tasks relate to the high level abstractions such as blacklisting and API keys
  • System tasks relate to low level abstractions such as the message queue and event log.
  • Node tasks relate to index node specific tasks, such as crawling and indexing.

Central Classes

See Also