I’m wanting to get some thoughts on the architecture side of how we could
increase the availability of Pulsar for producers. We’re running into an
interesting problem with some of our teams where Pulsar is occasionally not
available when they attempt to produce a message. There have been discuss
I was going through the producer api listed here:
https://pulsar.apache.org/docs/en/client-libraries-websocket/#producer-endpoint
It looks like the message payload can only be BASE64 encoded.
What if my message payload is in avro format?
Is there a way to use websocket api to send such a message.
Dear Pulsar enthusiast,
Last year, we conducted a Pulsar User Survey, the survey results reveal
Pulsar’s accelerating rate of global adoption, details how organizations
are leveraging Pulsar to build real-time streaming applications, and
highlights key features on Pulsar’s product roadmap.
To fur
