Tag Info

Hot answers tagged


Essentially you would need to proxy that web service with one of your own that does rate limiting. The devices wouldn't know anything about each other, and you can cache/re-implement the service if you need to scale further.


If your app is going to have a very small user base (say a corporate app, with less than a few hundred users), then you can make each client rate-limit itself to check the server less than once every N/100 seconds, where N = number of clients. Add in a little extra delay as a margin of safety, and perhaps randomize that margin a bit to lower the likelihood ...


Your web requests should be reasonably large chunks of data, i.e. a complete customer object rather than an individual field, or a complete invoice rather than each individual line item. It's not hard to see why this is true; the granularity of a web page that displays an invoice should be the same as the granularity of the data being displayed. Otherwise, ...


Design and build a REST API first. Be careful -- it really isn't as easy as it looks. Stateless, cacheable, resource identifiers not addresses. Not that easy. Then simply implement by abstracting over the concrete implementations you've already done. You will have to make tech choices, but you haven't told us anything about your contraints. For example, ...

Only top voted, non community-wiki answers of a minimum length are eligible