mirror of
https://github.com/MarginaliaSearch/MarginaliaSearch.git
synced 2025-02-23 21:18:58 +00:00
09917837d0
Wrapping these exceptions in a try-catch and logging them with slf4j will ensure they end up in the process logs. The way it worked using the default exception handler, they'd print on console (which nothing captures!), leading to a very annoying debugging experience. |
||
|---|---|---|
| .. | ||
| api | ||
| common | ||
| features-convert | ||
| features-crawl | ||
| features-index | ||
| features-qs | ||
| features-search | ||
| libraries | ||
| process-models | ||
| processes | ||
| services-application | ||
| services-core | ||
| tools | ||
| readme.md | ||
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.
Services
- core services "macroservices", stateful, memory hungry doing heavy lifting.
- application services "microservices", stateless providing additional functionality and making an application out of the search engine.
-
- api - public API
-
- search - marginalia search application
- an internal API
Processes
Processes are batch jobs that deal with data retrieval, processing and loading.
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.