isn't it limited to 10 000 requests a day? Assuming you build something that becomes popular, than that limit will be soon reached. What you going to do when that happens? Re-write it with something of your own?
If you are writing a small-ish webapp, then fine, but if you are building something that is going to be popular (or at least you are hoping it will), then using that API doesn't seem a good idea.
Java, Php, Python all have pretty decent chart generator apis that can do the same, or even more, so I really don't see the point of using the google api.
Basically, there is no 10,000 request limit. but, even if there was one, it would still be very easy to cache 10,000 unique graphs on the server, and then serve them up without making new requests to the chart API. Here's an excerpt from its Terms of use:
4.5 You acknowledge and agree that while Google may not currently have set a fixed upper limit on the number of transmissions you may send or receive through the Services or on the amount of storage space used for the provision of any Services, such fixed upper limits may be set by Google at any time, at Google's discretion.
Use of the Google Chart API is subject to a query limit of 50,000 queries per user per day. If you go over this 24-hour limit, the Chart API may stop working for you temporarily. If you continue to exceed this limit, your access to the Chart API may be blocked.
the request to the chart's url will be made by the client browser, which is a unique ip for practically every visitor. so, maybe that's 50,000 charts per day per visitor? unfortunately they don't really clarify what they mean, as they could be tracking the request referrer.
If you are writing a small-ish webapp, then fine, but if you are building something that is going to be popular (or at least you are hoping it will), then using that API doesn't seem a good idea.
Java, Php, Python all have pretty decent chart generator apis that can do the same, or even more, so I really don't see the point of using the google api.