spring-cloud / spring-cloud/spring-cloud-gateway
Rsocket & Websocket in Webflux mode on Spring Cloud
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
In my opinion, at the moment, one of the weaknesses of the Spring framework is the failure to finish Rsocket and Websocket in Webflux mode for Spring-cloud-gateway, even making a message broker that supports Rsocket and Reactive HTTP at the same time. In addition to adding these affairs, adding general maps automatically like Redis for keeping Websocket or Rsocket sessions easily helps developers broadcast data across these sessions through multiple machines.
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 proposal concerns spring-cloud-gateway in WebFlux mode and mentions RSocket, WebSocket, reactive HTTP, and Redis-backed session maps. Start by reviewing the gateway's existing WebFlux routing and session support, then clarify the required broker and multi-machine broadcast behavior. Done would require an agreed scope and acceptance tests for RSocket/WebSocket support and shared sessions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, redis, spring, spring-boot
- Domain
- api, backend, distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100