4 ms·

You guys really need to do this on GCP where there's zero Postgres competition. Since GCP will be overtaking AWS in like 2-3 years (hah), good to get a head st

You guys really need to do this on GCP where there's zero Postgres competition. Since GCP will be overtaking AWS in like 2-3 years (hah), good to get a head start now. ;)

craigkerstiens 11y ago
Thanks for the input, we're very much considering other infrastructure providers to run on. All input and requests for specific providers is helpful input for how we prioritize.
- leFrank 11y ago
  +1 for GCP. Managed/scalable Postgres would be amazing there.
- brandur 11y ago
  > Plans start at $1,800 a month, with the introductory plan including a total of 48 GB of memory for your database (one primary node and two compute nodes, each with 16 GB of RAM and two cores). You may need something that's a little more cost accessible before it's widely useful ;)
  - vbit 11y ago
    +1 Or you may want to allow a one-click solution that I can deploy on my resources now and later seamlessly move to your hosted solution, when I need to scale.
discodave 11y ago
Are you being sarcastic or do you really think GCP could overtake AWS in 2-3 years? That kind of growth would make the growth of AWS look like a local corner-store.
- NetStrikeForce 11y ago
  pbarnes_1 said she/he works for Google :-)
- pbarnes_1 11y ago
  I don't know about overtake, but GCE is IMHO far superior to EC2 in terms of both performance (both hardware and network) and price right now. And they keep dropping the price by 30% pretty much every year. I expect to see a shift to GCP over time, yes. Re Citus: Considering that you get 2 GB of bandwidth per core on GCE, that makes a lot of sense for a distributed DB like Citus where there's a lot of inter-node traffic. That other point there is that the maximum amount of RAM for a VM is 208Gb, which is not enough to scale up a Postgres instance. So a barrier to entry is porting your entire data layer to Datastore -- that's a significant engineering challenge that most people are unlikely to take up. So Citus would fit in really well. IMHO focusing on AWS (where Amazon are providing their own DB services) is missing an opportunity on GCP (where Cloud SQL is MySQL based and fairly limited).

You guys really need to do this on GCP where there's zero Postgres competition. Since GCP will be overtaking AWS in like 2-3 years (hah), good to get a head start now. ;)

craigkerstiens 11y ago

Thanks for the input, we're very much considering other infrastructure providers to run on. All input and requests for specific providers is helpful input for how we prioritize.

leFrank 11y ago
+1 for GCP. Managed/scalable Postgres would be amazing there.
brandur 11y ago
> Plans start at $1,800 a month, with the introductory plan including a total of 48 GB of memory for your database (one primary node and two compute nodes, each with 16 GB of RAM and two cores). You may need something that's a little more cost accessible before it's widely useful ;)
- vbit 11y ago
  +1 Or you may want to allow a one-click solution that I can deploy on my resources now and later seamlessly move to your hosted solution, when I need to scale.

discodave 11y ago

Are you being sarcastic or do you really think GCP could overtake AWS in 2-3 years? That kind of growth would make the growth of AWS look like a local corner-store.

NetStrikeForce 11y ago
pbarnes_1 said she/he works for Google :-)
pbarnes_1 11y ago
I don't know about overtake, but GCE is IMHO far superior to EC2 in terms of both performance (both hardware and network) and price right now. And they keep dropping the price by 30% pretty much every year. I expect to see a shift to GCP over time, yes. Re Citus: Considering that you get 2 GB of bandwidth per core on GCE, that makes a lot of sense for a distributed DB like Citus where there's a lot of inter-node traffic. That other point there is that the maximum amount of RAM for a VM is 208Gb, which is not enough to scale up a Postgres instance. So a barrier to entry is porting your entire data layer to Datastore -- that's a significant engineering challenge that most people are unlikely to take up. So Citus would fit in really well. IMHO focusing on AWS (where Amazon are providing their own DB services) is missing an opportunity on GCP (where Cloud SQL is MySQL based and fairly limited).