4 ms·

The Nth story about that guy who runs a business depending on Google services and suddenly starts telling everyone else they shouldn't run their business on Goo

by nokya 10y ago

The Nth story about that guy who runs a business depending on Google services and suddenly starts telling everyone else they shouldn't run their business on Google services because Google services flagged them and they realized it was a bad idea to run a business based on Google services...

ocdtrekkie 10y ago
Yup. This is note even a remotely surprising story. If you're building your business on Google, you're building your business to be arbitrarily shut down. You should not operate any business critical service or store any business critical data on any Google product or service. If anything, this is one of the more generous stories, because Google gave them a day or two of notice first. Usually you just find your Google account shut down one day.
- pg_is_a_butt 10y ago
  building services on Google Cloud that could also be ported to AWS or Azure or Docker or private servers is incredibly easy. Google Cloud in many cases is nearly free, or very cheap... use them while you can, flip the switch and tell the world if they screw you over. using Google App Engine, Cloud SQL, and the built in Memcache services costs a few dollars a month. using AWS Elastic Beanstalk with RDS and ElastiCache can cost upwards of $40/month. Both of these services are meant to scale, and the costs scale as well. If you're building your business spending more money than you need to, you're building your business to arbitrarily go bankrupt.
- Kadin 10y ago
  Well, I wouldn't go that far. If you run your business on Google Services, you definitely need to have a contingency plan for what you're going to do the day that Google decides to arbitrarily cut you off, though. But in some instances it might be financially worthwhile to take advantage of their services (particularly their free or very cheap ones) as long as you have a plan for standing up something else when that happens. For instance, I'm pretty comfortable using Gmail, even though I know they might someday pull the plug on my account for no particular reason. I'm comfortable doing that because all my mail is backed-up elsewhere, and in a pinch I could restore everything or stand up a new mailserver in a day. It would be obnoxious, sure, but it's not exactly breaking new technical ground or anything. The years of free service I've gotten out of them make that risk manageable. I could easily see a company taking that bargain for various other services. The problem becomes when you simply rely on a 3rd-party's infrastructure as if it was your own.

by nokya 10y ago

ocdtrekkie 10y ago

Yup. This is note even a remotely surprising story. If you're building your business on Google, you're building your business to be arbitrarily shut down. You should not operate any business critical service or store any business critical data on any Google product or service. If anything, this is one of the more generous stories, because Google gave them a day or two of notice first. Usually you just find your Google account shut down one day.

pg_is_a_butt 10y ago
building services on Google Cloud that could also be ported to AWS or Azure or Docker or private servers is incredibly easy. Google Cloud in many cases is nearly free, or very cheap... use them while you can, flip the switch and tell the world if they screw you over. using Google App Engine, Cloud SQL, and the built in Memcache services costs a few dollars a month. using AWS Elastic Beanstalk with RDS and ElastiCache can cost upwards of $40/month. Both of these services are meant to scale, and the costs scale as well. If you're building your business spending more money than you need to, you're building your business to arbitrarily go bankrupt.
Kadin 10y ago
Well, I wouldn't go that far. If you run your business on Google Services, you definitely need to have a contingency plan for what you're going to do the day that Google decides to arbitrarily cut you off, though. But in some instances it might be financially worthwhile to take advantage of their services (particularly their free or very cheap ones) as long as you have a plan for standing up something else when that happens. For instance, I'm pretty comfortable using Gmail, even though I know they might someday pull the plug on my account for no particular reason. I'm comfortable doing that because all my mail is backed-up elsewhere, and in a pinch I could restore everything or stand up a new mailserver in a day. It would be obnoxious, sure, but it's not exactly breaking new technical ground or anything. The years of free service I've gotten out of them make that risk manageable. I could easily see a company taking that bargain for various other services. The problem becomes when you simply rely on a 3rd-party's infrastructure as if it was your own.