<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Rate Limiting on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/rate-limiting/</link><description>Recent content in Rate Limiting on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Sat, 20 Aug 2022 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/rate-limiting/atom.xml" rel="self" type="application/rss+xml"/><item><title>Traffic Restriction Using Linux TC</title><link>https://www.chenshaowen.com/en/blog/traffic-restriction-using-linux-tc.html</link><pubDate>Sat, 20 Aug 2022 00:00:00 +0000</pubDate><atom:modified>Sat, 20 Aug 2022 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/traffic-restriction-using-linux-tc.html</guid><description>1. Traffic Control Principles Under Linux By queuing packets, we can control how data packets are sent. This kind of control is called data shaping (shape the data), and it includes the following operations on data:
Adding latency Dropping packets Reordering Duplicating, corrupting Rate control Under the qdisc-class-filter structure, controlling traffic requires three steps:</description><dc:creator>微信公众号</dc:creator><category>Linux</category><category>TC</category><category>Traffic Control</category><category>Operations</category><category>Network</category><category>Learning</category><category>Rate Limiting</category><category>Troubleshooting</category></item><item><title>How to Bypass DockerHub Image Pull Limits</title><link>https://www.chenshaowen.com/en/blog/how-to-cross-the-limit-of-dockerhub.html</link><pubDate>Wed, 09 Dec 2020 00:00:00 +0000</pubDate><atom:modified>Wed, 09 Dec 2020 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/how-to-cross-the-limit-of-dockerhub.html</guid><description>1. DockerHub Limits In the end, there is no getting around this error:
1 Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit Starting November 2, 2020, DockerHub officially began limiting the pull rate for non-paying users:</description><dc:creator>微信公众号</dc:creator><category>Docker</category><category>Images</category><category>DockerHub</category><category>Operations</category><category>Troubleshooting</category><category>Rate Limiting</category><category>Proxy</category></item><item><title>API Rate Limiting for Backend Services</title><link>https://www.chenshaowen.com/en/blog/rate-limiting-of-api.html</link><pubDate>Thu, 11 Jan 2018 00:00:00 +0000</pubDate><atom:modified>Thu, 11 Jan 2018 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/rate-limiting-of-api.html</guid><description>1. Flow Control Caching, degradation, and rate limiting are common methods for protecting high-concurrency systems. Caching trades space for time and cuts the time spent on CPU and network calls; degradation protects the high availability of core services by delaying or refusing to handle non-core requests during peak periods; rate</description><dc:creator>微信公众号</dc:creator><category>API</category><category>Microservices</category><category>R&amp;D</category><category>Architecture</category><category>Rate Limiting</category></item></channel></rss>