I think your biggest problem will be suppressed, knowing that you can set restrictions on the use of these services. If you click this limit, the service will return an error and you can handle it in your application.
40 requests per second used for all users and devices. If you had 3600 users, and they all pinged the server once an hour, this would be about 1 second. While this is not enough to create a service like facebook, instagram or twitter, this is likely to be enough to get meteorological data, a daily schedule or truck locations. For up to 4,000,000 users, the free tier will cover every user who checks no more than once every three hours with a uniform distribution.
2GB data transfer intended for all your users. Since scaling does not take effect until you have 100,000 users, 2 GB of data transfer is a pretty good amount to get you out of the ground. Since it scales at a speed of 50 MB per user, it is easy to see how much you can trust your application to communicate with the server. If only one user logs in, but you are still under shared use, you will not be charged. If you do upgrade, it will be $ 0.10 / GB data transfer.
You can restrict your application to communicate only this way until the user pays for the premium service. If you allow 50 MB / user / month of data transfer and tell the user when they are close to the limit that they will have to pay, you will never go over. You can also have ads on the device, which essentially pay for the service for scaling, thereby allowing users who use the application to have more privileges than passive users, but still allowing everyone to have basic use.
Prices are at the bottom of this page and are quite reasonable. You can definitely get a cheaper bet if you build things yourself and use AWS, but you need to be in the millions of users and / or have high requirements so that this is the best option.
Fennelouski
source share