So here's our use case: We have firmware that connects to server (simple php file - that takes post request) and add the data (350-500 bytes per request) to database.
Now here's a issue we have 3k units in the market and non-technical manager wants server to be able to handle 3k concurrent connections in worst case. Current it can handle around 600-650 connections (VPS 8GB NVMe - 6 core CPU (3.1 GHz) - 8GB NVMe RAM - 100GB NVMe SSD and 4TB bandwidth) costs around $100/month.
To scale up/scale out the cost is going to be enormous especially in the future when they are expecting 100k-500k units (which will again be a worst case).
Now good thing is that even if firmware fails to connect to server it can try reconnecting after 1 min/3 min and so on.. until the data is pushed - doesn't really hinders user experience at all. That's what I have been trying to convince them to do. Any other tips?
And let's say if we were to scale to that level what would be server I should look into.