This might sound silly, but what about DNS? It has caching built-in and we won't ever have to worry about load.
I could lookup the TXT entry for small.ec2.prices.libcloud.org, for example. Just my crazy 2 cents. On Wed, Jun 2, 2010 at 10:56 AM, Paul Querna <[email protected]> wrote: > Hi, > > I've had this random chat with half a dozen people at this point. > > Basically, the idea is to publish a JSON file with a size -> price > mapping for each provider. This data would be pushed up to an http > server 'somewhere' on the internet. > > When provider X changes their prices, we would just push up new json > files, and libcloud copies around the universe would fetch this on > demand. > > Thoughts on the basics? > > This makes it easier to make a 'long stable' version of libcloud, > because right now we will need to be pushing a new release every > month, because some provider is always changing pricing. > > Obviously, we would want to cache the file on the libcloud client > side, and ideally give people a way for people to change the URL, > thinking of a few functions on the top level module, something like: > > libcloud.price_cache_update() > libcloud.price_cache_set_url() > > "where' to publish this file might be the hardest question, I'd like > to do it on ASF resources, but that might cause some issues on the > infrastructure side, as they have been burned in the past by some java > projects hammering servers for dumb files. > > Thanks, > > Paul >
