Apache Pulsar Committer Β· Distributed messaging Β· API gateway Β· AI infrastructure
I work on the plumbing that moves data at trillion-message scale β the parts of the stack where one bad cache eviction policy costs a cluster its tail latency.
- 𧩠Apache Pulsar Committer β broker load balancing (traffic-based
BundleSplit), Broker Cache redesign with mark-delete eviction (hit rate 60% β 90%), BookKeeper stability fixes - π¨ 175+ pull requests across the Apache ecosystem β Pulsar (109), BookKeeper (42), Kafka (20), APISIX (4)
- ποΈ Middleware & AI infrastructure architect β API gateway platforms on APISIX, service-governance control planes, model-key lifecycle & AI gateway infrastructure
- π€ Speaker at ApacheCon Asia 2022 and Pulsar Summit Asia
- π Hong Kong SAR Β· English / δΈζ
| Project | Role | What I work on |
|---|---|---|
| Apache Pulsar | Committer | Load balancing & BundleSplit, Broker Cache eviction, write throttling, BookKeeper blacklisting & data migration |
| Apache BookKeeper | Contributor | Storage-layer fixes behind Pulsar at large scale |
| Apache Kafka | Contributor | Replication, consumer behaviour, protocol compatibility |
| Apache APISIX | Contributor | Gateway plugins for auth, rate limiting and traffic control |
I read the source before I file the bug β most of my patches start in the JIRA thread and end in a benchmark table.
| Project | Pull requests | Where it landed |
|---|---|---|
| Apache Pulsar | 109 | broker load balancing, cache eviction, write throttling |
| Apache BookKeeper | 42 | storage-layer stability under Pulsar's write path |
| Apache Kafka | 20 | replication, consumer behaviour, protocol compatibility |
| Apache APISIX | 4 | gateway plugins: auth, rate limiting |
Numbers from author:lordcheng10 PR searches β most of the code I ship lives upstream, not in my own repos.
Most of my code lives upstream β if you want to see the interesting parts, start with the Pulsar PRs.