Does docker swarm cluster support publisher / reader pattern
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 135
- Forks
- 27
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 8
Description
I am new to this events project, want to understand whether docker swarm cluster support publisher / reader pattern. I am looking for way working like this:
- there is a docker cluster, take swarm cluster as example.
- I can setup a client listener, which is connect to the cluster, my client can be notified automatically no matter what changes in the cluster, like new node joined, new images pulled, new container start/ stop, etc.
Does this event project support this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is an unanswered capability question rather than a scoped change, and it names no files or tests. Start by reviewing the event publisher/reader behavior and whether Docker Swarm changes are represented; done would require a maintainer-confirmed support answer or a separately scoped implementation issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100