In general we allow applications that integrate with Slack to send no more than one message per second. Consequently, maintaining a semblance of state persistence requires a storage backend so each iteration of the environment can be initialized. With few exceptions, its environment is completely constructed from scratch for each request.
Hardware appliances can limit the rate of requests on. 1 Hardware appliances 2 Web Servers 3 See also 4 References. In computer networks, rate limiting is used to control the rate of traffic sent or received by a network interface controller and is used to prevent DoS attacks. I tried my hand at a custom class that can help you deal with rate limiting downloads, you could try the following? class Downloader containers that pass requests to your app servers (PHP-FPM, mongrel, etc.).
I suggest setting up a cron job that executes every minute, or even better use Laravel scheduling rather than using sleep or usleep to imitate a cron. How does it work? You create a throttle, and ask it how long you should wait.
What is it? Stiphle is a little library to try and provide an easy way of throttling/rate limit requests, for those without fancy hardware etc. composer require davedevelopment/stiphle.
