Google Compute Engine: Expanded availability, new features, and lower prices

#1

Post by valhallarecords » Thu, Apr 04, 2013, 5:17 PM UTC

Google Compute Engine: Expanded availability, new features, and lower prices
googledevelopers.blogspot.com

Re: Google Compute Engine: Expanded availability, new features, and lower prices

#2

Post by thomasjames » Thu, Apr 04, 2013, 6:07 PM UTC

Does anyone know what the effective bandwidth and latency would be between machines? They talk about thousands of cores a little too casually. I guess they mean unrelated independent instances of some task as opposed to actual parallelism. I am confused as to what market segment they are going for here.

Re: Google Compute Engine: Expanded availability, new features, and lower prices

#3

Post by icey » Thu, Apr 04, 2013, 6:23 PM UTC

After being bitten a few times by Google unceremoniously shutting down services, it feels like unnecessary risk-taking to build software on their infrastructure.

Re: Google Compute Engine: Expanded availability, new features, and lower prices

#4

Post by bane » Thu, Apr 04, 2013, 6:28 PM UTC

icey wrote: post #3

After being bitten a few times by Google unceremoniously shutting down services, it feels like unnecessary risk-taking to build software on their infrastructure.

Google's done a great job shutting down much used and loved services. Perhaps it'd be a good idea for them to get behind what they're committed to supporting long term and make some public commitments.

Re: Google Compute Engine: Expanded availability, new features, and lower prices

#5

Post by yanw » Thu, Apr 04, 2013, 6:29 PM UTC

icey wrote: post #3

After being bitten a few times by Google unceremoniously shutting down services, it feels like unnecessary risk-taking to build software on their infrastructure.

Difference is you actually have to pay for this one.

Re: Google Compute Engine: Expanded availability, new features, and lower prices

#6

Post by ww520 » Thu, Apr 04, 2013, 6:35 PM UTC

yanw wrote: post #5

icey wrote: post #3

After being bitten a few times by Google unceremoniously shutting down services, it feels like unnecessary risk-taking to build software on their infrastructure.

Difference is you actually have to pay for this one.

AppEngine was a pay service too but price rise pretty much forced many people out.

Re: Google Compute Engine: Expanded availability, new features, and lower prices

#7

Post by ldargin » Thu, Apr 04, 2013, 6:37 PM UTC

thomasjames wrote: post #2

Does anyone know what the effective bandwidth and latency would be between machines? They talk about thousands of cores a little too casually. I guess they mean unrelated independent instances of some task as opposed to actual parallelism. I am confused as to what market segment they are going for here.

According to this review, their bandwidth is high and latency low, compared to EC2: http://bit.ly/Z3Peob

Re: Google Compute Engine: Expanded availability, new features, and lower prices

#8

Post by [deleted] » Thu, Apr 04, 2013, 6:46 PM UTC

yanw wrote: post #5

icey wrote: post #3

After being bitten a few times by Google unceremoniously shutting down services, it feels like unnecessary risk-taking to build software on their infrastructure.

Difference is you actually have to pay for this one.

[deleted]

Re: Google Compute Engine: Expanded availability, new features, and lower prices

#9

Post by yanw » Thu, Apr 04, 2013, 6:47 PM UTC

ww520 wrote: post #6

yanw wrote: post #5

Earlier quoted context omitted.

Difference is you actually have to pay for this one.

AppEngine was a pay service too but price rise pretty much forced many people out.

GAE had to become self-sustaining and now it's less of a risk for its customers. Google wants GCE to compete with AWS so pricing will be have to be competitive.

Re: Google Compute Engine: Expanded availability, new features, and lower prices

#10

Post by declan » Thu, Apr 04, 2013, 6:47 PM UTC

icey wrote: post #3

After being bitten a few times by Google unceremoniously shutting down services, it feels like unnecessary risk-taking to build software on their infrastructure.

When has Google shut down a paid service that was popular and under heavy development like GCE and GAE?

They may have, I admit, but I can't think of any. The point is raising the standard Google Reader/Google Buzz/etc. free examples isn't really apropos.