Urgent.News

What's breaking now, across thousands of outlets.

More in Tech

API Rate Limiting: What Actually Breaks When You Get It Wrong

Most teams add rate limiting to their API as an afterthought — usually right after something has already gone wrong. A scraper hammers an endpoint, a client integration goes into a retry loop, or a…

  • Simply setting a single request limit is insufficient as all requests don't have equal costs.
  • Centralize rate limit counters across multiple instances to prevent overloading the system.

At the edge, the number that matters is memory - not throughput (specially in Ramageddon)

We rebuilt LF Edge eKuiper in Rust and ran it against eKuiper, Telegraf and Redpanda Connect on five real MQTT workloads — one core, 1 GB of memory, and output checked message-by-message.

  • Memory usage, not throughput, is key metric in resource-constrained environments
  • Rekuiper, Rust-based engine, maintained memory usage between 5 and 10 MB
  • Design choices include bounded queues, incremental window aggregation, offline sink cache

More from Sunday 13 September →