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.
Google Compute Engine: Expanded availability, new features, and lower prices
21–30 of 54 posts
Re: Google Compute Engine: Expanded availability, new features, and lower prices
#22After 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.
It has to do with margins and focus. Companies time and time again sell /shut down profitable divisions, simply because they're not performing "good enough," whatever that may mean. Google essentially has no competition in advertising so anything else is a joke compared to that. Who knows?
Re: Google Compute Engine: Expanded availability, new features, and lower prices
#23Still waiting for naked domains...
Re: Google Compute Engine: Expanded availability, new features, and lower prices
#24Does anyone have experience in deploying Rails app to both Amazon EC2 and Google App Engine? How was your experience in terms of price, speed and easiness of deploying/maintaining?
Re: Google Compute Engine: Expanded availability, new features, and lower prices
#25These are paid services but before I'd jump in, Google would have to guarantee this service for say 5 years, with updates and no catch (like increasing the price by 5000% to force you out.) Microsoft is a lot of things, but one they do good is guaranteed, long term, support for their products. At least for the core ones. For example they are still supporting Windows XP, so when Coca Cola signs at the dotted line they…
As part of their pricing switch a few years ago, Google committed to a 3 year depcreation period for App Engine: http://googleappengine.blogspot.com/2011/05/year-ahead-for-g...
"For App Engine, leaving Preview will include providing all paid users a 99.95% uptime service level agreement, operational and developer support, billing via invoice, a new Terms of Service agreement geared towards businesses, and a new, easier to understand usage-based pricing structure for App Engine that is in line with the value App Engine provides. It will also reaffirm our deprecation policy whereby we will support deprecated versions of product APIs for 3 years, allowing applications written to prior API specifications to continue to function."
A quick comparison of the TOS shows that Compute Engine doesn't have the same policy, but IANAL, so I could be missing something.
Re: Google Compute Engine: Expanded availability, new features, and lower prices
#26Is anyone actually using compute engine here? Would be interested in your experiences. The scalr reference point sounds like payola to me.
Re: Google Compute Engine: Expanded availability, new features, and lower prices
#27Does anyone have experience in deploying Rails app to both Amazon EC2 and Google App Engine? How was your experience in terms of price, speed and easiness of deploying/maintaining?
I haven't looked at AppEngine lately but I believe you cannot run Rails on it. It has its own proprietary service and API that you have to write against. It's not like EC2 where you pretty much can install anything and do whatever.
Re: Google Compute Engine: Expanded availability, new features, and lower prices
#28These are paid services but before I'd jump in, Google would have to guarantee this service for say 5 years, with updates and no catch (like increasing the price by 5000% to force you out.) Microsoft is a lot of things, but one they do good is guaranteed, long term, support for their products. At least for the core ones. For example they are still supporting Windows XP, so when Coca Cola signs at the dotted line they…
As part of their pricing switch a few years ago, Google committed to a 3 year depcreation period for App Engine: http://googleappengine.blogspot.com/2011/05/year-ahead-for-g... "For App Engine, leaving Preview will include providing all paid users a 99.95% uptime service level agreement, operational and developer support, billing via invoice, a new Terms of Service agreement geared towards businesses, and a new, easi…
it looks like you get one year from announcement of deprecation: https://developers.google.com/compute/docs/terms (see 7.3)
Compute Engine also isn't really in the same realm of worry as App Engine, for some, at least. Most of what you're getting is immediately migrateable if it's going to be shut down, as opposed to app engine, where there are some migration paths to similar stacks, but no flip-a-switch path to converting existing code and data to a "standard" stack (at least from my understanding. I haven't tried compute engine).
Re: Google Compute Engine: Expanded availability, new features, and lower prices
#29Earlier quoted context omitted.
AppEngine was a pay service too but price rise pretty much forced many people out.
It's not so much the difference between free and paid that matters as whether or not the pricing is actually economically viable. The original GAE pricing pretty obviously wasn't, so it might as well have been a free product in that you were relying on Google continuing to want to subsidize it for whatever reason.
How do we as customers know whether a pricing posted by a company is viable or not? What is the criteria for viability? Someone didn't get his bonus because of growth not meeting target? Or the engineering budget has blown up passed expectation?
It doesn't mean those will not happen again.
Re: Google Compute Engine: Expanded availability, new features, and lower prices
#304% seems underwhelming given regular double digit reductions from amazon