1. That's untrue. Partitions are limited to what a machine may handle, but topics may be scaled across many ordered partitions.
2. This is generally handled by the client library transparently. Have you ever needed to manage this state manually?
2. This is generally handled by the client library transparently. Have you ever needed to manage this state manually?
That said, curious to hear your experiences :)
Outside of librdkafka and jvm client, it’s gloves off.
IIRC Confluent has started putting resources into it - I would hope so, given how .NET Core is going.
That said, the state of Pulsar clients outside of the official Java ones was far worse, I was looking into .NET Core ones and the "official" one (Pulsar-DotPulsar) lacked some key features, whereas a third party one, pulsar-client-dotnet, had far more features, but was still somewhat behind the Java clients.
Caveat is that I looked into all of this when Pulsar was at version 2.6, it's not at 2.7.1, so my comments may well be out of date.