CatgirlIntelligenceAgency/code
Viktor Lofgren a0f28a7f9b (*) Add a barebones configuration
This adds a docker-compose file 'docker-compose-barebones.yml' which will only start the minimal number of services needed to run a whitelabel Marginalia Search-style search engine, with none of the surrounding frills.

The change also adds a minimal search GUI to the query service, which is also available with JSON results if the appropriate Accept header is provided.
2024-01-10 20:23:51 +01:00
..
api (control) Add a 'cancel' button to the process list 2024-01-10 15:02:42 +01:00
common (search) Serve proper content type for static resources 2024-01-10 10:46:51 +01:00
features-convert (keyword-extractor) Add another test for Name-extractor 2024-01-01 15:21:51 +01:00
features-crawl (converter) Fix NPEs in converter due to the new data format 2023-12-28 22:54:53 +01:00
features-index (loader) Update the size of the keyword files created by the loader 2024-01-10 17:09:19 +01:00
features-qs (search/index) Add a new keyword "count" 2023-12-25 20:38:29 +01:00
features-search (*) Replace EC_DOMAIN_LINK table with files and in-memory caching 2024-01-08 15:53:13 +01:00
libraries (control) Add a 'cancel' button to the process list 2024-01-10 15:02:42 +01:00
process-models (crawl data) Add compatibility layer for old crawl data format 2024-01-08 19:16:49 +01:00
processes (loader) Update the size of the keyword files created by the loader 2024-01-10 17:09:19 +01:00
services-application Merge pull request #69 from MarginaliaSearch/converter-optimizations 2024-01-10 09:46:54 +01:00
services-core (*) Add a barebones configuration 2024-01-10 20:23:51 +01:00
tools (crawl data) Add compatibility layer for old crawl data format 2024-01-08 19:16:49 +01:00
readme.md (docs) Improve architectural documentation 2023-11-30 21:38:57 +01:00

Code

This is a pretty large and diverse project with many moving parts.

You'll find a short description in each module of what it does and how it relates to other modules. The modules each have names like "library" or "process" or "feature". These have specific meanings. See doc/module-taxonomy.md.

Overview

A map of the most important components and how they relate can be found below.

image

The core part of the search engine is the index service, which is responsible for storing and retrieving the document data. The index serive is partitioned, along with the executor service, which is responsible for executing processes. At least one instance of each service must be run, but more can be run alongside. Multiple partitions is desirable in production to distribute load across multiple physical drives, as well as reducing the impact of downtime.

Search queries are delegated via the query service, which is a proxy that fans out the query to all eligible index services. The control service is responsible for distributing commands to the executor service, and for monitoring the health of the system. It also offers a web interface for operating the system.

Services

Processes

Processes are batch jobs that deal with data retrieval, processing and loading. These are spawned and orchestrated by the executor service, which is controlled by the control service.

Tools

Features

Features are relatively stand-alone components that serve some part of the domain. They aren't domain-independent, but isolated.

Libraries and primitives

Libraries are stand-alone code that is independent of the domain logic.

  • common elements for creating a service, a client etc.
  • libraries containing non-search specific code.
    • array - large memory mapped area library
    • btree - static btree library