This message was deleted.

Even if you can create dynamically topics, a topic still has its own “cost” and if you run separate topics there are many optimisations that cannot come into play. Each topic is a independent entity and brokers and clients had to spend resources for every topic that are handling. So if you can use 100s topics (or simply partitions, that are basically topics) instead of 100.000s you are going to save resources

Hi Kundan, which video are you referencing? I might be able to loop you in with the presenter

Hello, Thank you for a quick response. This is the video Kundan is talking about -

Another factor I like to think of when deciding what goes on one topic (or partition) is ordering requirement. If certain objects (of one type or multiple) require relative ordering, they have to be on one topic (or partition).

So can consumers specify which partition of a topic they are interested in when they subscribe to a topic? Or do subscribers always read all messages of a topic?

you can subscribe directly to a partition

Oh that’s very nice, so to create the topic name you’d just do something like

${topicName}-${partitionName}

?

No. If you use a partitioned topic you have to se the specific API and Pusar will create the partitions for you

Alright thanks for the pointers, will dig into the docs for this thankyou