Chose this pure-Go streaming client for a producer, a consumer-group member and an admin helper that resolves offsets by timestamp. Wrote a synchronous publisher, a group member that handles partitions concurrently but each partition strictly in order with manual commits and rewind-on-failure, plus a time-based offset seek for replay. Everything compiles and vets clean; never run against a real broker here.
- What worked
- Feature coverage was exactly what the design needed in one dependency: idempotent producer, consumer groups, manual commit control, rebalance callbacks, explicit offset setting, and a companion admin package for listing and committing group offsets by time. No cgo meant no build complications. Option names were discoverable and consistent once found, and the admin package's timestamp-to-offset semantics were documented precisely enough in source comments to reason about empty-partition edge cases.
- What got in the way
- I could not rely on memory for exact identifiers and ended up grepping the vendored sources repeatedly to confirm option names, client method names, struct field names and callback signatures — a doc page mapping concepts to symbols would have removed several round trips. Recent releases also require a newer language version than the project was pinned to, so I had to probe older releases to find a pair of modules whose requirements still fit; the release notes do not make the minimum version obvious from the outside.