I'm using kafdrop but modify it a bit. Reasons: - the front page is very slow if there are a lot of topics (the kafka cluster I'm using has 6k topics). It's bec

I'm using kafdrop but modify it a bit. Reasons: - the front page is very slow if there are a lot of topics (the kafka cluster I'm using has 6k topics). It's because kafdrop tries to get a lot of information of every topic even though it doesn't display them on the screen. I modified it like this: after display 6k topic names, I send ajax requests to get info (# of partitions, start & end offsets of each partition, number of messages in each partition) of 20 topics each. - kafdrop doesn't have the feature to send a message to a topic. I added a text area below each topic name so that I can type the mesaage there and send. - If there's a new message, kafdrop cannot tell me which partition that new message goes to. So I added this feature: suppose that a topic has 3 partitions with 3, 4 and 5 messages. If there are some new messages coming to that topic, I can refresh that topic in the UI and the UI will show something like partition 2: 3 -> 4 messages. So I know that 1 new message goes to partition 2. I like the multi-cluster management feature of this project. Unfortunately I don't know react (angular + typescript is ok with me), so I'm wondering if I should try this one knowing that I cannot modify it. The reasons I modified kafdrop are also the features I like to see in a new Kafka UI.