How is calls per minute supposed to scale?

  • 1
  • Question
  • Updated 4 years ago
Currently this limitation on the API severely limits what someone can do with it. Like for instance I do not think this scales for a web or mobile app that may want to have a map of data. Currently with your pricing you limit me to 10k users per minute. That's actually only if I manage to make an app that needs a single call. That comes down to around 6 cents per user for the best price and 20 cents for the others. In reality this actually is multiplied many times because a user requires multiple api calls.

I am a little baffled as to who made this decision and how you expect users to actually use the API.

Am I missing something that I should know before I even think about using the service?
Photo of Joey

Joey

  • 2 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of WunderWilliam

WunderWilliam

  • 267 Posts
  • 18 Reply Likes
Are you going to have a map of a region, with separate temp results, and that's why you need multiple calls for each user?

You could cache the results on your end and serve them to multiple users within a region. That would save a bunch of calls.
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 122 Reply Likes
You can also request multiple features at one time, such as /conditions/geolookup/forecast/ all at the same time.
Photo of Joey

Joey

  • 2 Posts
  • 0 Reply Likes
I realize I can request multiple features but this is limited to features per location as far as I could tell.

Also I guess if one has their own backup server making the requests they can cache the data but this may only work for finding the current weather in a large area.

My use case is more localized to places that people engage in sporting activities. The users would want to know the current (as up to date as possible) conditions for many locations. I actually am not even concerned with features like forecast as much as I am about weather (Wind specifically) very close to key sites.

The whole calls per minute really messes this up and the requirement to cache means a lot more work and it still means it sub-accurate data.

It also means that if a developer has a small number of users to start (all over) that I as the developer would quickly have to upgrade the account and pay a monthly fee that would probably outweigh the income of the application.

I suppose I could cache the data per site and only update it if I know the site data has been updated if the polling frequency of that station was known. But at this point I am recreating the database you already have (and paying for it).

Seems that using the service for a little more than a regional weather app is impossible for a smaller app developer.

Do you provide a sandbox environment that allows one to develop and test is code without limitations even if it was mock data?
Photo of WunderWilliam

WunderWilliam

  • 267 Posts
  • 18 Reply Likes
We don't have a sandbox environment available, but we have a free dev key to try stuff out.

The subscription levels won't work for all use cases. It's quite possible that our API won't be an ideal choice for your project.