Recent AWS Customer Success Stories & Videos

More AWS Customer Success Stories...

« IntrIdea Rolls out Scalr, Updates MediaPlug, Builds Community | Main | Cloud Camp, and More »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341c534853ef00e552b75c4d8834

Listed below are links to weblogs that reference The Emerging Cloud Service Architecture:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Peyman

Can you provide some rough numbers for intra-cloud bandwidth and latency vesus inter-cloud? Maybe intra-cloud services would make a better name for this.

Mr Jones

This is future speculation, but I have a question: Do amazon always plan to charge when their cloud compute service access another cloud compute service (for instance Google App Engine).

It seems to me that via strategic location of servers (in common data centers) and other measures these costs could be reduced (if not eliminated).

Perhaps this an unfair (or over simplistic) re-phrasing of the question but does amazon see cross provider cloud compute working like IP protocol or like a walled garden (where every time an application migrates data/processing between a provider it incurs a cost for doing so?)

Jared

One thing I'd love to see is the option to provide a service in the cloud that I don't get charged for per se - rather, the user of the service pays for it. Ideally, the service provider can indicate something like 5 cents per invocation, and the service user gets charged 5 cents + the cost to the cloud owner to actually run the service. That way both the cloud owner and I would get paid.

The advantages to a service provider is pretty clear. For one, the service provider wouldn't be spending money running a service that doesn't get used (outside costs to develop and test it initially). Additionally, billing becomes the job of the cloud, which greatly simplifies things.

I'm not sure it works out so well for a cloud owner. One could argue that the cloud provider shouldn't make a distinction between "applications" and "services", as both are code running in the cloud, and it makes more financial sense to charge both. I believe it would ultimately be beneficial from the point of view that given the benefits of scaling (cloud owner with largest infrastructure ultimately can provide lowest cost) it makes sense for cloud owners to get the largest and best set of cloud services. And the best way to do that would be to make the cloud the best one for service providers to work with.

The comments to this entry are closed.

Featured Events

The AWS Report


Brought to You By

Jeff Barr (@jeffbarr):



Jinesh Varia (@jinman):


Email Subscription

Enter your email address:

Delivered by FeedBurner

April 2014

Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30