MarginaliaSearch/code/services-core/query-service
Viktor Lofgren 66c1281301 (zk-registry) epic jak shaving WIP
Cleaning out a lot of old junk from the code, and one thing lead to another...

* Build is improved, now constructing docker images with 'jib'.  Clean build went from 3 minutes to 50 seconds.
* The ProcessService's spawning is smarter.  Will now just spawn a java process instead of relying on the application plugin's generated outputs.
* Project is migrated to GraalVM
* gRPC clients are re-written with a neat fluent/functional style. e.g.
```channelPool.call(grpcStub::method)
              .async(executor) // <-- optional
              .run(argument);
```
This change is primarily to allow handling ManagedChannel errors, but it turned out to be a pretty clean API overall.
* For now the project is all in on zookeeper
* Service discovery is now based on APIs and not services.  Theoretically means we could ship the same code either a monolith or a service mesh.
* To this end, began modularizing a few of the APIs so that they aren't strongly "living" in a service.  WIP!

Missing is documentation and testing, and some more breaking apart of code.
2024-02-22 14:01:23 +01:00
..
src (zk-registry) epic jak shaving WIP 2024-02-22 14:01:23 +01:00
build.gradle (zk-registry) epic jak shaving WIP 2024-02-22 14:01:23 +01:00
readme.md (doc) Update docs 2024-02-06 12:41:28 +01:00

The query service parses search queries and delegates work to the index services.

The index-service speaks a lower level query specification language that is difficult to build an application out of. The query service exists as an interpreter to that format.

Web Interface

The query service also offers a basic web interface for testing queries, or running the search engine as a white-label service without all the Marginalia Search specific stuff. This mode of operations is available through a barebones install.

The web interface also offers a JSON API for machine-based queries.

Main Classes

See Also