Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by rpedela on Friday August 05, 2016 @04:28PM
(#12235525)
For me, it is primarily about Postgres. If Google Cloud had an equivalent offering to Postgres RDS then I would seriously consider it. I think RDS is one area where AWS is significantly better than many of their competitors. You can use any of the major relational databases and they handle backup, failover, read slaves, encryption at rest, etc.
[ Parent
| on HN ]
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by boulos on Saturday August 06, 2016 @01:06AM
(#12237110)
We hear you (and all of you downthread) and we naturally happen to build what people ask for. Thanks for comments like these though, the PMs here literally link to HN all the time (if you want to help more you can ping them with "and my AWS bill was $XXk this month").
Disclosure: I work on Google Cloud, so I'll probably come back to you and hold you to this statement...
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by jacques_chester on Saturday August 06, 2016 @09:51AM
(#12238106)
I'm mostly glad to hear that you have product managers. A lot of what comes from Google just seems to be engineering wandering randomly in and out of the latest shiny thing.
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by matrix on Friday August 05, 2016 @04:47PM
(#12235646)
Ditto. If Google offered an equivalent of RDS PostgreSQL, I'd switch tomorrow.
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by boulos on Saturday August 06, 2016 @01:06AM
(#12237116)
Even if it were in Alpha / Beta? What if it didn't have point-in-time recovery, etc.? Just looking for when we can pencil you in ;)
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by meddlepal on Friday August 05, 2016 @07:06PM
(#12236276)
Dear GCP Product Managers are you listening?! Please add this :)
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by deesix on Saturday August 06, 2016 @02:01AM
(#12237242)
Yes. We are listening.
Disclosure: I work on GCP
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by rprime on Friday August 05, 2016 @11:38PM
(#12236911)
Same. We just switched to Amazon mostly due to Postgres RDS (and $100k in credits, but that's another story). When Google will get their Postgres game on, we'll switch for sure.
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by vincentdm on Friday August 05, 2016 @07:26PM
(#12236356)
Me too!
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by sjellis on Saturday August 06, 2016 @03:50AM
(#12237452)
Another vote for PostgreSQL. I've recently completed an AWS migration project, am about to start another, and really wish that I could have pitched GCP. The two reasons that I didn't were the "Beta" tags on things (in particular, App Engine Flexible Environment), and the situation with hosted SQL (1st gen vs. 2nd gen, both MySQL-only).
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by Jweb_Guru on Tuesday August 09, 2016 @11:06AM
(#12255010)
Same.
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by tracker1 on Friday August 05, 2016 @05:47PM
(#12235941)
I wish compose.io would flush out their product line on DO, GCE and Azure... If you're mainly wanting PostgreSQL, database labs will support custom deployments, should be able to get it on GCE.
Along similar lines, I really find Azure SQL tempting to use as well, may test the latency from DO's SFO location to Azure's West US.
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by gingerlime on Saturday August 06, 2016 @12:17AM
(#12236996)
First I hear of databaselabs.io but looks interesting. I wonder why they don't seem to offer HA option (at least didn't see it mentioned).
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by tracker1 on Saturday August 06, 2016 @01:19AM
(#12237150)
Probably a matter of their flushing out their tooling... not sure, in my case the continuous backups would be enough for my personal projects.
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by agrafix on Saturday August 06, 2016 @04:36AM
(#12237524)
Same here, biggest reason to be in AWS is Postgres RDS which works like a charm!
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by yeukhon on Friday August 05, 2016 @05:28PM
(#12235853)
Yet, RDS can't scale up much. You are stuck with a fixed number of HA instances, and a fixed number of read replica. You want a cluster of twenty nodes, roll your own.
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by rpedela on Friday August 05, 2016 @05:56PM
(#12235987)
Did you ask them to increase the limit? They usually increase the limit (regardless of service) if you ask. The current limit is 40 instances and 5 read replicas per master.
http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_L...
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by tracker1 on Friday August 05, 2016 @05:49PM
(#12235951)
This is one area I think Azure does shine... Azure's storage tables, blob and queues are dead simple and inexpensive to work with, and Azure SQL is priced better than any cloud db competitor.
Keeping hobby projects under $10-20/month is sometimes hard...
Re:Why We Moved from Amazon Web Services to Google Cloud Pla...
by chaostheory on Friday August 05, 2016 @04:48PM
(#12235655)
This is the reason that keeps me from trying Google Cloud as well. Not to mention a lot of 3rd party services aren't on Google Cloud yet either.