argoproj/argo-events

WebSocket EventSource

Open

#1,567 opened on Jan 27, 2022

View on GitHub
 (0 comments) (12 reactions) (0 assignees)Go (829 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (2,679 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe. I was browsing through the list of supported EventSources, and couldn't find the right connector. Specifically, I wanted to try and get these events: https://stream.meetup.com/2/rsvps

I understand that some streaming APIs might also behave in this manner.

Describe the solution you'd like An EventSource for streaming APIs that uses websockets as a connection.

Describe alternatives you've considered Stream processors that can be written in Spark, Flink etc. But that's overkill in my opinion. I can write my own listeners, but if it's a streaming JSON API, it might be good to standardize on it.

Additional context API Endpoint Example: https://stream.meetup.com/2/rsvps But generally, I think this proposed EventSource should use the websocket protocol to connect and just send the messages to the EventBus. I can write the code if this enhancement gets accepted.

Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Contributor guide

Research direction
Study existing EventSource implementations (e.g., HTTP, SNS) in Argo Events to understand the interface and lifecycle. Then implement a new EventSource that establishes a WebSocket connection to the provided URL, receives messages, and publishes them to the EventBus. Use the Meetup stream API as a primary example.
Tech stack
gokubernetes
Domain
backendinfrastructurecloud
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesArgo Events
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65