From d1fd0b8e6d34bee5220f087713de12a7fbc56e29 Mon Sep 17 00:00:00 2001 From: Gabriel Manor Date: Wed, 25 Sep 2024 15:18:24 +0300 Subject: [PATCH] Update run_opal_with_pulsar.mdx --- documentation/docs/tutorials/run_opal_with_pulsar.mdx | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/documentation/docs/tutorials/run_opal_with_pulsar.mdx b/documentation/docs/tutorials/run_opal_with_pulsar.mdx index 8f069beb..4433d7a6 100644 --- a/documentation/docs/tutorials/run_opal_with_pulsar.mdx +++ b/documentation/docs/tutorials/run_opal_with_pulsar.mdx @@ -17,10 +17,10 @@ OPAL-server can scale out both in number of worker processes per server and acro ### Broadcaster Module -Support for multiple backbone solutions is provided by the [Python Broadcaster package](https://pypi.org/project/broadcaster/). To use it with Apache Pulsar, install the `broadcaster[pulsar]` module: +Support for multiple backbone solutions is provided by the Permit's port of the [Python Broadcaster package](https://pypi.org/project/permit-broadcaster/). To use it with Apache Pulsar, install the `permit-broadcaster[pulsar]` module: ```bash -pip install broadcaster[pulsar] +pip install permit-broadcaster[pulsar] ``` ## Setting Up OPAL-server with Apache Pulsar @@ -102,7 +102,6 @@ You should see the effect in: You can trigger events by publishing messages directly to the 'broadcast' topic in Pulsar. Ensure the message format follows the OPAL-server schema for backbone events. - ## Conclusion This guide covered setting up and using Apache Pulsar as the backbone pub/sub for OPAL-server. By following these instructions, you can effectively scale your OPAL deployment across multiple servers.