Commit information, not traffic. I’m building VSA (Vector–Scalar Accumulator), a new primitive that turns noisy per‑request writes into net, bounded commits—cutting write amplification and hot‑row contention in high‑throughput systems.

Why this is novel

Most limiters/counters persist every event (token/leaky bucket, naive batching). VSA persists only the net effect on a controlled cadence. In benchmarks, this yields orders‑of‑magnitude fewer DB calls on hot keys with near‑zero hot‑path cost—translating to big savings on per‑request stores and calmer p95s.

About me

I’m a backend engineer and applied researcher with extensive experience in core banking and large‑scale telecom (AT&T, Cisco). I love tackling hard concurrency and data‑systems problems and turning them into practical, well‑tested tools.

Why sponsor

Your support accelerates:

• Production‑grade adapters (Redis today; DynamoDB/Postgres next)
• Invariants, docs, and e2e demos for real deployments
• Observability (OTel metrics + Grafana dashboards) and a simple ROI calculator
• Hardening under hot‑key skew, churn, and multi‑node scenarios

Who benefits

API platforms, quota/rate‑limit services, and any team paying per write or fighting hot‑row contention.

If VSA helps you ship faster, spend less, or sleep better during peak traffic, sponsoring sustains the research and the engineering to make it rock‑solid for everyone. Thank you!