5 ms·
There are vendors running managed Postgres services on Google Cloud Platform, like ElephantSQL [1] and Aiven [2]. And you can of course run your own on GCE, ev
by crb 11y ago
There are vendors running managed Postgres services on Google Cloud Platform, like ElephantSQL [1] and Aiven [2]. And you can of course run your own on GCE, even to the extent of 24/7 commercial support - you can run EnterpriseDB from Cloud Launcher [3].
And, you can also run Kubernetes on AWS - we have a group focused on making sure it's an excellent experience.
I work for Google Cloud Platform; ping me if you'd like more help with either option.
[1] https://www.elephantsql.com/blog/2014-11-17-google-compute-engine.html https://www.elephantsql.com/blog/2014-11-17-google-compute-e...
[2] https://aiven.io/ https://aiven.io/
[3] https://cloud.google.com/launcher/solution/public-edb-ppas/edb-postgres-enterprise?q=enter https://cloud.google.com/launcher/solution/public-edb-ppas/e...
- dsacco 11y agoYou don't have contact info in your profile.
- crb 11y agoFixed, thanks!
- waffle_ss 11y ago> There are vendors running managed Postgres services on Google Cloud Platform, like ElephantSQL I did check out ElephantSQL but my pricing needs are somewhere between their $100 and $20 plans and there seems to be a lack of configurability compared to RDS's parameter groups (e.g. enabling extensions). > you can also run Kubernetes on AWS I've had success turning up Kubernetes clusters on AWS for demo purposes, but I really don't want to manage a k8s cluster myself (anecdotes I've read about etcd failures / partitions especially scare me). Also I use Terraform for provisioning, and kube-up.sh is not something that fits into that paradigm. I've also made the mistake running kube-up.sh with the wrong arguments after a previous invocation that had created a cluster, which caused it to try and create a new cluster, which wiped the local cache of the previous cluster I had made, making kube-down.sh unable to automatically clean up the old cluster (so I had to do it manually in the AWS console). The other thing I tried was the kube-aws CoreOS tool, which is nice, but it comes baked with a 90-day expiration due to TLS certificate expiration, so I'd have to set up some sort of PKI process to make that production-ready. All in all just too much work for a single person trying to deploy a small number of containers for small to medium sized projects; if I was a medium-sized company with hundreds of containers and some dedicated DevOps resources maybe it would be worth it, but for myself I'd prefer a turn-key solution like ECS or GKE.
- TheIronYuppie 11y agoWe also just had a user check in a cloud formation template for Kubernetes on AWS - would that meet your needs? (No kube-up.sh required) Disclosure: I work on GKE and Kubernetes at Google
- merb 11y agoYou can't compare that to postgresql on aws. especially not when it comes to pricing.
- seanp2k2 11y agoIMO one of the benefits of a platform service is that you get the whole platform from one vendor, so if you're having some problem, you can work with one vendor to sort it out. Trying to get Google support to work with a 3rd-party vendor and my hypothetical company on an issue sounds like a nightmare. There are already many other options for platform services which provide e.g. Everything you'd need to run a Rails app in dev and prod, so that's where the bar is.
- lobster_johnson 11y agoI sincerely hope you will add PostgreSQL support to CloudSQL soon. The current Postgres offerings are not great. ElephantSQL is extremely expensive compared to their offering: 4 cores, 15GB RAM, 1TB data for $1,000/mo. CloudSQL (2nd gen) with the exact same specs would be $370/mo. Aiven doesn't advertise exact prices until you sign up, so I can't compare, but I see that the number of instances (max 3 nodes) is very small, so not really an option.