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.
[ Parent
| on HN ]
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).