watermill

watermill copied to clipboard

Would be nice to have a curated list of third-party libraries written for Watermill. For example I was looking for a Zap adapter for the logger and found this after...

sagikazarmark

- Added an `_example/pubsub/nats-jetstream` based on https://github.com/ThreeDotsLabs/watermill-jetstream - Ran `make validate_examples` (hence all the go dep changes) - Updated `dev/validate-examples` to use `gopkg.in/yaml.v3` (formally v2) possibly a little premature considering...

VeryStrongFingers

Any plans for supporting GKE Workload Identity for Google Pub/Sub

1

## Overview I was hoping I can leverage [GKE Workload Identity](https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity) instead of generating the service account keys via a JSON file. I gave it a shot today, but it...

faraonc

Multiple topics, same handler

4

I have multiple topics and 1 generic handler that sends those messages to an external system. For example: Topics: `user_topic`, `post_topic`, `comment_topic` Handler: `send_to_segment_handler` The router currently has a check...

odannyc

Fix #275

1

This PR contains a fix for the issue but for now other PubSub tests are broken (eg. TestResendOnError). I may have misunderstood how the Ack/Nack mechanism is supposed to work....

upils

## Context Apart from low-level `Publisher` and `Subscriber` interfaces, Watermill users can use either `Router` or the CQRS component. After considering how we were using Watermill over the years and...

m110

[watermill-kafka] why message doesn't resend when consumer group don't send ACK

1

when consumer group got message from kafka topic and process, some error happen then consumer don't call msg.Ack() , why this message don't resend again, just resend when i restart...

suhoangson

When passing a nil DB the code that checks the db == nill is false because the beginner is an interface so the nil DB satisfies the interface but is...

dubyte

Apache Pulsar Pub/Sub implementation

3

roblaszczak

`kafka.Subscriber.Close()` seems not concurrent safe. `close(s.closing)` may be executed multiple times when called concurrently, causing `panic: close of closed channel `. https://github.com/ThreeDotsLabs/watermill-kafka/blob/9242094c8fd755f501295c65515f2d47bb122962/pkg/kafka/subscriber.go#L468 ``` func (s *Subscriber) Close() error { if...

xuyang2