集群限流和redis集群限流的性能对比数据有吗
Open
area/cluster-flow
area/performance
kind/discussion
- Dominant language
- Java
- Stars
- 23.1k
- Forks
- 8.1k
- PR merge metrics
- No merged PRs in 30d
Description
感谢,如题;请教下关注的集群限流下的几个问题
(1)这里的TokenServer既然是单点部署的,必然存在性能瓶颈,和采用redis来做集群限流的优势在哪里呢?
(2)TokenServer的IP地址是写死的,那么嵌入模式下,系统重启发布该怎么办,如何做到业务无感知同时保证正确性呢?
(3)每个请求的限流检查都要经过TokenServer,如何解决热点namespace问题?
(4)既然开源出来推荐给大家用,目前缺乏一些性能压测数据,还是说只是给大家提供了一种思路,生产环境有使用的案例吗?
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Research the TokenServer and Redis cluster rate-limiting designs and any available benchmark or production-use material; done means documenting performance comparisons and answering the four deployment, restart, hotspot, and usage questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, redis
- Domain
- distributed-systems, documentation, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100