opensabre / opensabre/base-sysadmin
feat: 发布字典变更事件并支持应用缓存主动失效
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1
- Forks
- 3
- Avg merge
- 4h 24m
- Merged PRs (30d)
- 11
Description
问题
字典修改后应用侧只能等待本地 TTL 或手动刷新，无法及时感知变更，容易出现多实例数据不一致。
工作项
- 定义字典变更事件（字典编码、版本、变更时间等）
- 提供可靠发布机制与失败重试
- Framework 订阅后按字典粒度失效或刷新缓存
- 处理重复、乱序、丢失事件，并保留 TTL 兜底
验收标准
- 字典变更可在约定时限内传播到所有活跃实例
- 重复/乱序事件不造成旧值回写
- 有跨实例集成测试与监控指标
关联
- #10
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing issue #10 and tracing the existing dictionary update, cache, and event-handling paths in the repository. Identify the entry points for publishing changes and for Framework cache invalidation before defining the cross-instance integration tests and monitoring metrics. Done means timely propagation, safe handling of duplicate or out-of-order events, retries, and TTL fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100