Why WebSocket Rate Limiting Breaks Real-Time Apps

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

Why WebSocket Rate Limiting Breaks Real-Time Apps

Listen for free

View show details

Lucas and Luna dive into the overlooked failure mode of WebSocket rate limiting. Most API rate limiting is built for HTTP request-response cycles, but WebSockets are persistent bidirectional streams — applying HTTP-style limits causes silent disconnects, missed messages, and unpredictable backpressure. They examine how Discord's gateway handles 120,000 concurrent WebSocket connections with per-connection token bucket rate limiting, and why GitHub's real-time Events API had to shift from connection-based to event-rate-based quotas after developer complaints about ghost disconnections. The episode covers concrete patterns like sliding window counters vs. token buckets, the hidden cost of closing connections without sending a '429' equivalent, and why the WebSocket spec's lack of built-in rate limiting forces every team to reinvent the wheel. #WebSocket #RateLimiting #RealTimeAPI #DiscordGateway #GitHubEvents #TokenBucket #SlidingWindow #Backpressure #WebSocketSpec #APIDesign #DeveloperExperience #Infrastructure #DevTools #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #LucasAndLuna #TheDeveloperToolsPodcast Keep every episode free: buymeacoffee.com/fexingo

No reviews yet