#Ballerinax/Redis to implement the pub/sub mechanism

1 messages · Page 1 of 1 (latest)

bleak thicket
#

Is there a way to use Ballerinax/Redis to implement the pub/sub mechanism? How can it be implemented?

worn walrus
#

Looping in @grizzled surge @balmy flame

balmy flame
celest nacelle
celest nacelle
#

This does not use any broker, just a plain publisher, subscriber package. You can integrate this to any implementation.

noble dock
celest nacelle
#

@noble dock We use pubsub to publish/subscribe to a particular topic. In this implementation, a pipe (xlibb/pipe) instance is used as a broker, basically, an in-memory message queue. This can be used to publish/subscribe asynchronously inside the same application. Seems like your requirement is different here. In your case, the Ballerina Kafka library maybe a solution? But then again, you have to have a Kafka broker up and running.

There are no message brokers implemented in Ballerina currently.

stable vale
#

@celest nacelle UGH that's the wrong answer. Using an in-memory "broker" is not useful for many scenarios.

Ballerina has connectors to Kafka, RabbitMQ, Azure Service bus, any JMS broker and various others. There's also a websub hub (written in Ballerina itself and backed by Kafka) that you can use if you want to do webhook based pub/sub.

@bleak thicket if the Redis connector needs to add more stuff that can be done too (I'm not familiar with Redis pub/sub).