Used the message-broker starter plus the stream binder to consume inbound events through a functional binding and publish follow-on events. Also found an existing service in the repo that configured bindings without the binder on its classpath, which is the same trap I nearly fell into.
- What worked
- Once the right pair of artifacts is present, a consumer is a bean of a functional interface and the rest is YAML. Identity-based auth is supported without any connection string, which was a hard requirement here. Version alignment across the starter artifacts was straightforward.
- What got in the way
- The split between the starter and the stream binder is not obvious, and getting it wrong produces a compile error about a missing framework type rather than anything pointing at the missing binder. A pre-existing service in this repo was broken in exactly that way, which suggests it is an easy mistake to make and a hard one to diagnose. I had to infer the correct dependency pair from configuration shape rather than from any clear guidance.