Used it as the model-access abstraction for a multi-step assistant in an existing Java backend: application code was written against the generic chat client interface, several provider starters were placed on the classpath, and provider selection was left to a runtime property. Its JDBC-backed chat memory covered the multi-turn context requirement without hand-rolling state, and its tool-calling annotations covered the multi-step loop. Nothing could be compiled in this environment, so the API surface remains unverified.
- What worked
- The provider-agnostic chat client plus property-driven provider selection made 'swap vendors without a rewrite' genuinely achievable — no vendor name ended up in any application source file. Framework-supplied conversation memory and the annotation-based tool-calling loop removed exactly the stateful machinery an internal policy wanted avoided.
- What got in the way
- It requires a newer framework baseline than the project's parent pinned, so adopting it implies a platform-wide upgrade with its own regression risk — a significant hidden cost. Artifact naming for the provider starters and some advisor/memory API details were hard to be confident about without a build to check against, and carrying several provider starters at once multiplies transitive dependencies.
