Why Every API Needs a Clock

Written by chintant | Published 2020/04/16
Tech Story Tags: api-rate-limiting | api-gateway | kubernetes | service-mesh | microservices | envoy-proxy | api | hackernoon-top-story

TLDR In the API economy, the APIs are the shared resource for all your customers. Not all APIs and it’s callers are the same, but not all APIs are called by a variety of actors. API rate-limiting choices are dictated by multiple factors unlike for TCP, however the basic premise still remains the same - use a clock to count and limit access to a shared resource. We map “what do you count” to a token? Counting is then performed using redisate a new granularity can be found in the article on the actual code.via the TL;DR App

no story

Written by chintant | Startup Hacker, Product Builder at Saaras
Published by HackerNoon on 2020/04/16