kowl
gogen-avro
Our great sponsors
kowl | gogen-avro | |
---|---|---|
8 | 2 | |
2,675 | 358 | |
- | - | |
9.4 | 4.2 | |
over 1 year ago | 2 months ago | |
TypeScript | Go | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kowl
-
DragonFly - real time entity sentiment analysis
View on GitHub
- Managing Apache Kafka Connect via Kowl
- Show HN: UI for Apache Kafka
-
Kafka UI supports kraft mode
Maybe give kowl a try: https://github.com/cloudhut/kowl
- Kafka Web UI - Kowl v1.3.0 has been released
-
Feature complete Kafka client written in Go
More concrete, take a look at Kowl how it uses Franz Go to talk to the Admin API: https://github.com/cloudhut/kowl/blob/master/backend/pkg/kafka/list_consumer_group_offsets.go#L15-L22
gogen-avro
-
NoProto: Flexible, Fast and Compact Serialization with RPC
This seems pretty confused. The "compiled vs dynamic" distinction is a property of the implementation, not of the protocol.
For example, you can certainly compile Avro into Go source files [0]. You can even compile Avro loaded schemas _during runtime_ into Python bytecode, since Python is interpreted [1]. This even works if you have the _wrong schema document_ for the message (you'll just get the subset of fields which are accurately described), because of Avro's schema compatibility rules.
Likewise, you can deserialize arbitrary protobuf messages during runtime without a compilation step, if you have a description for the message schema. The Python protobuf library has had a "ParseMessage" API forever, and protoreflect [2] exists for Go. (In case it's not obvious, I mostly work in Python and Go but I am completely certain analogues exist in other major languages).
There is a very big and important difference between a protocol and the implementation of a protocol. I think this README's author is not clear on that difference, which shows up in other claims ("Deserialization is incrimental", for example) too.
---
[0] https://github.com/actgardner/gogen-avro
[1] https://github.com/spenczar/avroc
[2] https://pkg.go.dev/google.golang.org/protobuf/reflect/protor...
-
Feature complete Kafka client written in Go
at my company, we ended up writing a client on top of the Confluent client (which hooks into the librdkafka C library) and uses the gogen-avro library to provide type safe codegen for Avro schemas and is used for the serde process within the client. the API ended up looking basically like the standard Java API. as for feature parity, librdkafka seems to provide most of what we've needed from a Kafka producer/consumer config side of things while the SR implementation is limited in scope anyways and can easily be included in a basic library.
What are some alternatives?
kafka-ui - Open-Source Web UI for Apache Kafka Management
avroc - Python library for compiling Avro schemas into executable encoders/decoders
akhq - Kafka GUI for Apache Kafka to manage topics, topics data, consumers group, schema registry, connect and more...
NoProto - Flexible, Fast & Compact Serialization with RPC
kafka-manager - CMAK is a tool for managing Apache Kafka clusters
sarama - Sarama is a Go library for Apache Kafka. [Moved to: https://github.com/IBM/sarama]
Kouncil - Powerful dashboard for your Kafka. Monitor status, manage groups, topics, send messages and diagnose problems. All in one user friendly web dashboard.
plumber - A swiss army knife CLI tool for interacting with Kafka, RabbitMQ and other messaging systems.
dhtc - DHT crawler with web ui
kowldocs
dragonfly - Real time sentiment analysis on entities from scraped text.