5 ms·

Disclaimer: I work for Google Cloud > Cloud solutions like elastic load balancing are generally engineered for the average use case. Think about the ways you a

Disclaimer: I work for Google Cloud > Cloud solutions like elastic load balancing are generally engineered for the average use case. Think about the ways you are not like the average. This might be the case for some things, but many of Google Cloud's "elastic/serverless" products (Load Balancers, App Engine, Pub/Sub, BigQuery, Datastore, etc) can truly scale up from nothing to huge traffic spike without the need for pre-warming and things like that.

encoderer 9y ago
When I read that your load balancer is not individually provisioned the way Amazon's is I was envious. I couldn't imagine migrating to a new cloud provider now but I'm really impressed with what Google has put together!
- shusson 9y ago
  > I couldn't imagine migrating to a new cloud provider now ugh vendor lock-in is the worst :)
  - cobookman 9y ago
    You should talk to a gcp sales rep. They can help you move to a multi Cloud deployment. As well as describe some migration options.
nodesocket 9y ago
Came here just to reiterate this. Google Cloud Load balancers don't need warming, manual creation of support tickets, etc. Also, networking on GCP is vastly superior to AWS. The VPC is setup with sane defaults and VM instances can communicate privately to other VM instances in any zone or region without needing complicated constructs such as VPN's or NAT instances. Lastly, Google Cloud is generally cheaper (sustained use-discounts), higher performance, and takes all the lessons learned from AWS and applies them. The one knock I have on GCP is billing. It is incredibly obtuse. Even the monthly billing invoices I still have a hard time digesting (especially if you have multiple projects under a single billing account).
- NicoJuicy 9y ago
  This... To get even the invoices of Google apps ( suite) I have to download 12* 3€
- tyingq 9y ago
  Any AWS users have a better experience with their newer "ALB" load balancer? It doesn't specifically call out any performance benefits over the legacy "ELB", but since it's much newer, I'm curious if it happens to do better.
  - aluminussoma 9y ago
    Yes. Although Administration / UI is slightly more confusing. We had unique performance issues with the ELB offering that couldn't be fixed because it was the way it was designed. With ALB, that performance issue no longer existed.
    - mwcampbell 9y ago
      ALB may be more complicated, but it's also more flexible, and I've especially come to appreciate that in the past couple of days. By the way, it looks like ALB might be based on nginx, based on the error pages. I wonder if classic ELB is based on HAProxy.
- manigandham 9y ago
  > The one knock I have on GCP is billing. It is incredibly obtuse. Really? We've found it to be much easier. The billing section has up-to-date current breakouts and a simple list of transactions for each billing account. There are budget alerts and the best part is the easy export into bigquery which then gives you SQL access for all of it. Add in datastudio and you have BI style analysis and visualizations too. Better than anything else the other clouds have. Video from GCP Next: https://www.youtube.com/watch?v=qL8kvTb4RbU https://www.youtube.com/watch?v=qL8kvTb4RbU
blazespin 9y ago
Google Cloud is great and cheap. But AWS is waaay more ahead in terms of completeness. I've looked into this. The breadth, depth, and polish of AWS is really impressive. Their API Gateway -> lambda container -> DataStore is amazing. I really wish I could use GCP. :( Hopefully GCP will start pushing AWS to lower their prices. They charge so much.
- _0nac 9y ago
  Curious: How does that differ from GCP's Cloud Endpoints/Apigee Edge -> Cloud Functions -> Cloud Datastore? Disclaimer: I work for GCP.
  - tyingq 9y ago
    Some of it is just documentation and marketing. If you go to the AWS api gateway main page, it talks about serverless/lambda integration right there. They also have specific pages that show how to use them together. Including using them as the endpoint, or using them at a higher level to influence routing to a different endpoint, or modify requests, etc. Contrast with Google, you start with the confusion that there are two products (cloud endpoints, apigee), and neither really talks about integration with Cloud functions.
  - squeaky-clean 9y ago
    In my case the first obstacle (and I haven't looked into it too much) is we have a lot of Lambda functions written in Python and Scala.
- tyingq 9y ago
  The API Gateway is somewhat limited in that the endpoints are tied to CloudFront. So, if you want to leverage it internally, versus connections from a user's web browser, the request leaves your VPC (and potentially goes quite a ways out) for no obvious reason. It would be nice if they decoupled API gateway from CloudFront.
  - lostcolony 9y ago
jacques_chester 9y ago
I think there will eventually be a lot of headslapping blogposts from people who migrate to GCP. It really is that much better and still costs less. Where I work we are saving ... uh ... a lot of money by migrating our workloads over. And they're faster. It's awesome.

encoderer 9y ago

When I read that your load balancer is not individually provisioned the way Amazon's is I was envious. I couldn't imagine migrating to a new cloud provider now but I'm really impressed with what Google has put together!

shusson 9y ago
> I couldn't imagine migrating to a new cloud provider now ugh vendor lock-in is the worst :)
- cobookman 9y ago
  You should talk to a gcp sales rep. They can help you move to a multi Cloud deployment. As well as describe some migration options.

nodesocket 9y ago

Came here just to reiterate this. Google Cloud Load balancers don't need warming, manual creation of support tickets, etc. Also, networking on GCP is vastly superior to AWS. The VPC is setup with sane defaults and VM instances can communicate privately to other VM instances in any zone or region without needing complicated constructs such as VPN's or NAT instances. Lastly, Google Cloud is generally cheaper (sustained use-discounts), higher performance, and takes all the lessons learned from AWS and applies them. The one knock I have on GCP is billing. It is incredibly obtuse. Even the monthly billing invoices I still have a hard time digesting (especially if you have multiple projects under a single billing account).

NicoJuicy 9y ago
This... To get even the invoices of Google apps ( suite) I have to download 12* 3€
tyingq 9y ago
Any AWS users have a better experience with their newer "ALB" load balancer? It doesn't specifically call out any performance benefits over the legacy "ELB", but since it's much newer, I'm curious if it happens to do better.
- aluminussoma 9y ago
  Yes. Although Administration / UI is slightly more confusing. We had unique performance issues with the ELB offering that couldn't be fixed because it was the way it was designed. With ALB, that performance issue no longer existed.
  - mwcampbell 9y ago
    ALB may be more complicated, but it's also more flexible, and I've especially come to appreciate that in the past couple of days. By the way, it looks like ALB might be based on nginx, based on the error pages. I wonder if classic ELB is based on HAProxy.
manigandham 9y ago
> The one knock I have on GCP is billing. It is incredibly obtuse. Really? We've found it to be much easier. The billing section has up-to-date current breakouts and a simple list of transactions for each billing account. There are budget alerts and the best part is the easy export into bigquery which then gives you SQL access for all of it. Add in datastudio and you have BI style analysis and visualizations too. Better than anything else the other clouds have. Video from GCP Next: https://www.youtube.com/watch?v=qL8kvTb4RbU https://www.youtube.com/watch?v=qL8kvTb4RbU

blazespin 9y ago

Google Cloud is great and cheap. But AWS is waaay more ahead in terms of completeness. I've looked into this. The breadth, depth, and polish of AWS is really impressive. Their API Gateway -> lambda container -> DataStore is amazing. I really wish I could use GCP. :( Hopefully GCP will start pushing AWS to lower their prices. They charge so much.

_0nac 9y ago
Curious: How does that differ from GCP's Cloud Endpoints/Apigee Edge -> Cloud Functions -> Cloud Datastore? Disclaimer: I work for GCP.
- tyingq 9y ago
  Some of it is just documentation and marketing. If you go to the AWS api gateway main page, it talks about serverless/lambda integration right there. They also have specific pages that show how to use them together. Including using them as the endpoint, or using them at a higher level to influence routing to a different endpoint, or modify requests, etc. Contrast with Google, you start with the confusion that there are two products (cloud endpoints, apigee), and neither really talks about integration with Cloud functions.
- squeaky-clean 9y ago
  In my case the first obstacle (and I haven't looked into it too much) is we have a lot of Lambda functions written in Python and Scala.
tyingq 9y ago
The API Gateway is somewhat limited in that the endpoints are tied to CloudFront. So, if you want to leverage it internally, versus connections from a user's web browser, the request leaves your VPC (and potentially goes quite a ways out) for no obvious reason. It would be nice if they decoupled API gateway from CloudFront.
- lostcolony 9y ago

jacques_chester 9y ago

I think there will eventually be a lot of headslapping blogposts from people who migrate to GCP. It really is that much better and still costs less. Where I work we are saving ... uh ... a lot of money by migrating our workloads over. And they're faster. It's awesome.