HN user

db3pt0

15 karma
Posts0
Comments6
View on HN
No posts found.

A glucose tablet and a glucagon shot can both be used in emergencies, but they are best used to treat different levels of emergencies. You can take a glucose tablet if you're coherent and conscious, but when you're incoherent or passed out from a severe hypoglycemia, someone else administering a glucagon shot is a lot easier and safer.

A few pieces of feedback.

Positive:

  - Multi-cluster support is a great feature! That's the main thing missing from Kowl, in my opinion
  - The UI feels clean
  - Message streaming feels smooth, and the search feature is a great addition. Also love the ability to see a message for a given partition/offset, and that JSON messages are nicely rendered as JSON!
Negative/Feature Requests:
  - The CleanupPolicy logic doesn't handle "delete,compact" (I see bug number 829 addressed a slightly related issue, maybe that logic could be expanded [1])
  - When viewing Cluster -> Topic -> Consumers, it seems like far more is being loaded than just consumer groups for that particular topic. It takes much longer to load than, e.g., Kowl does for pulling the same information
  - Similar feedback for when clicking on an individual consumer group (example URL path: "/ui/clusters/dev/consumer-groups/my-group"). It takes a very long time to load
  - If any permissions issues are encountered while loading the individual consumer group, the entire request fails. That wouldn't necessarily be an issue, but it is when you're loading all consumer groups, and not just the one requested
  - I don't see any docs on how to access a topic that is secured with certificates (Kowl's relevant config [2])
  - If a schema registry uses a self-signed certificate (or one signed by a corporation's CA), there's no way to pass the certificate through a config or skip validation (Kowl's relevant config [3]). As it is, you get a 500 error in the API call, but the UI doesn't show an error
Overall, it seems like a fair bit of thought went into this! But there are a few quirks that make it very tough to use in a corporate environment with (perhaps excessively) large Kafka clusters with hundreds/thousands of topics, or secured with internal certificates

1. https://github.com/provectus/kafka-ui/blob/master/kafka-ui-a...

2. https://github.com/cloudhut/kowl/blob/10776b81e45abfa716548d...

3. https://github.com/cloudhut/kowl/blob/10776b81e45abfa716548d...