"Stop Rate Limiting! Capacity Management Done Right" by Jon Moore

You will like the Strange Loop 2017 talk about this subject: "Stop Rate Limiting! Capacity Management Done Right" by Jon Moore ▶ this video Concurrent capacity might not be the best metric.

Relevant to queueing theory: "Stop Rate Limiting! Capacity Management Done Right" by Jon Moore ▶ this video

* To Serve The People: Public Interest Technologists. Matt Mitchell is a hacker, security researcher, operational security trainer, and data journalist who founded & leads CryptoHarlem, impromptu workshops teaching basic cryptography tools to the predominately African American community in upper Manhattan. link * Stop Rate Limiting! Capacity Management Done Right. Jon Moore is the Chief Software Architect at Comcast Cable, where he focuses on delivering a core set of scalable, performant, robust software components for the company's varied software product development groups. ▶ this video * Keeping Time in Real Systems. This talk will tour the fascinating timekeeping mechanisms used in real systems. We will explore atomic clocks, NTP and GPS through systems that use them, and logical clocks in the context of systems built on logical time. link * Level Up Your Concurrency Skills With Rust. This talk will show you how Rust will catch many concurrency errors at compile time. link * Diablo: A Classic Game Postmortem. Diablo developer David Brevik returns to the GDC stage to give a classic post-mortem on Blizzard's action RPG hit Diablo in this 2016 talk. link * The Flash Games Postmortem . In this 2017 GDC talk, Kongregate's John Cooney attempts to encapsulate the immense history of Flash games and how it has shaped the current game industry by giving game developers their first chance to build and publish their games quickly to the web. link * Siege Battle AI in Total War:

For a different view on the topic watch "Stop Rate Limiting! Capacity Management Done Right" ▶ this video The basic premise is not do do req/s limiting but rather concurrency limiting which results in req/s limiting by itself. Concurrency limiting is rather simple and doesn't require a lot of code complexity.