💡 gRPC bridge for SSE fan-out — interest check

[sbharatjoshi]

Idea: gRPC-based SSE Bridge

Currently we support Redis Pub/Sub and Spring Cloud Stream for multi-pod fan-out. Would there be interest in a gRPC-based bridge for environments that already have gRPC infrastructure?

Potential benefits

• Lower latency than Redis Pub/Sub for direct pod-to-pod communication
• No broker dependency — direct gRPC streaming between pods
• Service mesh friendly — works with Istio, Linkerd out of the box
• Protobuf serialization — more efficient than JSON

Potential challenges

• Requires service discovery (or known peer list)
• More complex than broker-based approaches
• Partition tolerance is harder without a broker

Questions

1. Would you use a gRPC bridge over Redis/Kafka?
2. What service discovery would you expect? (Kubernetes, Consul, static list?)
3. Should it be push-based (streaming) or pull-based (polling)?

Upvote 👍 if interested, or share your thoughts below!