This message was deleted.

Hi @Robert Philp 🙂 By using Kafka as the backbone pub/sub for the OPAL-servers you can simply publish OPAL events on Kafka and have the OPAL-servers consume them (and propagate to the relevant clients) Check out the docs here: https://docs.opal.ac/tutorials/run_opal_with_kafka#triggering-events-directly-from-kafka Note that Kafka topics shouldn’t be confused with OPAL-topics (though they can share the same names)

Thanks @Or Weis. I had misunderstood the flow of this. So it is actually the OPAL server that consumes from this topic and then notifies the relevant clients of the change to go and fetch? The rest of this is using an event pattern, so I was keen to avoid every upstream microservice needing to know the OPA data context every other microservice needs. The example I'd seen was to have a topic per service, but actually keeping the OPAL topic names to match the event names, the OPAL-client can then subscribe to all the topics it needs, avoiding mixing patterns. This makes more sense. Thanks.

Happy to have helped 😊