Laravel Vapor feels like a perfect choice.
How to best handel 1500 requests a second
In our company, we developed our own cloud web application to gather data from sensors in real-time.
We have the following components:
Laravel 8, PHP 7.4, MySQL 8, Redis 5 used for the queues with horizon, laravel-websockets from beyondcode used to update displays in real-time
Currently, the whole application is hosted on a single droplet on digitalocean, which was not a problem till now, as we currently only receive 16 requests a second from about 40 sensors.
The problem is we need to add another 1000 sensors in December, and we estimate about 1500 requests a second.
We started optimizing our cloud for this high traffic, by hitting the database only when it is really necessary, and using caching when possible, we have also moved all the logic to handle the request from a sensor to a job so that we can queue it and return as soon as possible.
But I wanted to ask the experts here what would they suggest to do, first we want to switch to better infrastructure, like digital ocean kubernetes , or the new app platform, or even something else like amazon aws.
So many options and zero experience with high traffic, what would you suggest.
Please or to participate in this conversation.