Honestly, I'm more interested in auth callout, someone making a "how to use this stuff effectively" video and/or article, for dummies, ideally with keycloak.<p>If you look at [0] how does this explain anything? Seems like I need to write a service utilizing NATS which talks to the OIDC server.<p>NATS auth story is a complicated one, and now with auth callout it's even more complicated.<p>What I also quite didn't succeed in were JS client Jetstream consumers, async polling or w/e.
All the examples, async or sync would block execution.<p>The regular request/response with microservices went well and straightforward. No issues at all.
But writing middleware is also not very pretty, you have to have dedicated functions which you would call in the request handler (or microservice if you will) instead of being able to define a chain of middleware functions.
Potejto potato but organization and structure and naming is half the code.<p>And more now you can't rely on http error codes, even if you can use them.<p>Then debugging is difficult, because messages are sent in binary format, and with no middleware to conditionally plug in, it's even more painful. Yeah you could write a dedicated service listening to >.* and printing deserialized JSON payloads but that's also extra work.<p>However dropping the HTTP overhead leads to a lot more throughput.<p>For now I'll stay with HTTP.<p>The reason I experimented with it was there is a company which required NATS knowledge.<p>[0] <a href="https://docs.nats.io/running-a-nats-service/configuration/securing_nats/auth_callout" rel="nofollow noreferrer">https://docs.nats.io/running-a-nats-service/configuration/se...</a>