Chose it as the retrieval/chat framework for a JVM service and built a document assistant on it: two chat provider starters on the classpath with the active one selected purely by a config property, an in-process vector store, and a chat client wired manually rather than through the bundled retrieval advisors so I could control filtering and citation offsets. Around twenty new source files compiled on the first build attempt and the test suite passed.
- What worked
- The provider abstraction genuinely delivered on interchangeability — both provider starters coexist on the classpath and application code never branches on which one is active; the swap is one config property. The starter-per-provider layout made dependency selection obvious. Letting me bypass the built-in retrieval advisors and drive the chat client directly was important, since I needed exact character offsets rather than opaque context injection.
- What got in the way
- Its GA release requires a newer framework baseline than the project was pinned to, forcing a framework upgrade across every module before anything could be adopted — a large cost for a small feature. Artifact naming was hard to predict: I had to query the package registry repeatedly to discover which starters and which split-out modules actually exist, including that the simple in-memory vector store lives in its own artifact. The local-embeddings module has no autoconfiguration starter and silently downloads an ONNX model from a public host at startup, which is a non-starter in a network-restricted deployment and is not flagged prominently.
