5 ms·

Is the title peak buzzword-era, or is there more to come?

by pmlnr 7y ago

dna_polymerase 7y ago
The page greets you with: > Kubernetes Accelerated Your Path to Enterprise Cloud Native I have no idea what they want from me.
- djohnston 7y ago
  They want money!
LeonM 7y ago
Nah, it doesn't contain blockchain or serverless, so there is still some runway left.
minxomat 7y ago
This might be an elaborate demo for the upcoming thisblogpostdoesnotexist ML text synthesis project. Just for fun, I used Grover to generate an article based on the headline: > What is the cheapest way to optimize the cloud? Going globally? Using open-source cloud computing platforms? Choosing AWS in the U.S. and for the remaining countries? Choosing SaaS? Or, using AWS and establishing a global presence on the EC2 Container Manager platform? > I know because I did all four. And I won’t do them again. > I am not arguing that globalizing your compute resources through a community cloud is any less important than globalizing your compute resources through your enterprise cloud (though I am somewhat of a skeptic about the value of community clouds). The important point is that migrating to a global cloud requires a state-of-the-art approach to container-native load balancing, container-native load balancing on AWS, and container-native load balancing on other clouds. And you need to be prepared to pay for it.
- politelemon 7y ago
  Can you tell me a little more about Grover, is it a CLI you just pointed at a URL or a little bit more to generate that article?
  - minxomat 7y ago
    I have a local version of Grover and the model checkpoints, so I used a python script. But I think there's an online demo somewhere.
- DangitBobby 7y ago
  Okay, but unless Grover can accurately describe how to deploy services and load balancers on GCP, generate valid kubernetes yaml that matches the contents of the article, and generate an infrastructure diagram that matches the infrastructure described in the article, then this was certainly not generated by Grover. It in no way resembles something generated by some ML text synthesis. I'm not sure how anyone who read it could come to the conclusion that it was.
  - deleted 7y ago
    [deleted]
ljm 7y ago
I remember when load balancing was a case of setting up apache or nginx on a server and letting it handle the upstream connections.
- zzzcpan 7y ago
  It still is. Proper "global load balancing" is essentially a CDN and nginx with say bind9 running on a bunch of edge nodes from different hosting providers without all those container-native buzzwords is the easiest way to do it.
- manigandham 7y ago
  It still is... if you're just running a few apps on single server, or 1 load balancer VM in front of a few other servers. This article is talking about routing traffic from a single IP globally to multiple backend Kubernetes clusters that can be running in any region. Traffic will automatically go to the closest region (with available capacity) or otherwise fallback to other endpoints, while also bypassing much of the Kubernetes network stack to go straight to the running pods via GCP's software-defined network. The complexity here is warranted if you need the flexibility and features. If you don't then you can just stick with nginx.
ec109685 7y ago
I think that is unfair. Each of those buzz words were concepts in the article or actual products that GCP offers. However, this is embarrassing to GCP that this isn’t easier. These were very basic requirements from this customer, yet so much rigmarole was needed to get it set up.
- manigandham 7y ago
  Multi-cluster global load balancing isn't "very basic" and no other cloud is any easier. AWS requires stacking the Global Accelerator on top of their ALB/ELBs but doesn't have smart routing across clusters and Azure only has Frontdoor which requires completely manual setup and has no backend integration.
  - ec109685 7y ago
    Deploying an app to more than one geographic region on earth should be very basic. For mostly read only sites, it is mean to make your users suffer extra latency and your reliability goes down. The authors had to go read source code to figure out obscure annotations at one point to get container aware networking to work, which then wasn’t compatible with Google’s tools to setup global ingress.
    - manigandham 7y ago
      That isn't very basic and never has been. If it's just a read-only site then all you need is a CDN, not load balancing with multiple regions running Kubernetes clusters. What other cloud vendor or PaaS offers this? The only one that has seamless global deployment is Cloudflare's Workers but that's limited to Javascript code in a lightweight functions environment.
      - ec109685 7y ago
        They are making one part of this easier at least: https://twitter.com/vicnastea/status/1232751949117702145?s=20 https://twitter.com/vicnastea/status/1232751949117702145?s=2...
manigandham 7y ago
They are product and feature names used by the GCP platform (and this article). It's perfectly accurate and descriptive.

Is the title peak buzzword-era, or is there more to come?

by pmlnr 7y ago

Is the title peak buzzword-era, or is there more to come?

The page greets you with: > Kubernetes Accelerated Your Path to Enterprise Cloud Native I have no idea what they want from me.

djohnston 7y ago
They want money!

LeonM 7y ago

Nah, it doesn't contain blockchain or serverless, so there is still some runway left.

minxomat 7y ago

This might be an elaborate demo for the upcoming thisblogpostdoesnotexist ML text synthesis project. Just for fun, I used Grover to generate an article based on the headline: > What is the cheapest way to optimize the cloud? Going globally? Using open-source cloud computing platforms? Choosing AWS in the U.S. and for the remaining countries? Choosing SaaS? Or, using AWS and establishing a global presence on the EC2 Container Manager platform? > I know because I did all four. And I won’t do them again. > I am not arguing that globalizing your compute resources through a community cloud is any less important than globalizing your compute resources through your enterprise cloud (though I am somewhat of a skeptic about the value of community clouds). The important point is that migrating to a global cloud requires a state-of-the-art approach to container-native load balancing, container-native load balancing on AWS, and container-native load balancing on other clouds. And you need to be prepared to pay for it.

politelemon 7y ago
Can you tell me a little more about Grover, is it a CLI you just pointed at a URL or a little bit more to generate that article?
- minxomat 7y ago
  I have a local version of Grover and the model checkpoints, so I used a python script. But I think there's an online demo somewhere.
DangitBobby 7y ago
Okay, but unless Grover can accurately describe how to deploy services and load balancers on GCP, generate valid kubernetes yaml that matches the contents of the article, and generate an infrastructure diagram that matches the infrastructure described in the article, then this was certainly not generated by Grover. It in no way resembles something generated by some ML text synthesis. I'm not sure how anyone who read it could come to the conclusion that it was.
- deleted 7y ago
  [deleted]

ljm 7y ago

I remember when load balancing was a case of setting up apache or nginx on a server and letting it handle the upstream connections.

zzzcpan 7y ago
It still is. Proper "global load balancing" is essentially a CDN and nginx with say bind9 running on a bunch of edge nodes from different hosting providers without all those container-native buzzwords is the easiest way to do it.
manigandham 7y ago
It still is... if you're just running a few apps on single server, or 1 load balancer VM in front of a few other servers. This article is talking about routing traffic from a single IP globally to multiple backend Kubernetes clusters that can be running in any region. Traffic will automatically go to the closest region (with available capacity) or otherwise fallback to other endpoints, while also bypassing much of the Kubernetes network stack to go straight to the running pods via GCP's software-defined network. The complexity here is warranted if you need the flexibility and features. If you don't then you can just stick with nginx.

ec109685 7y ago

I think that is unfair. Each of those buzz words were concepts in the article or actual products that GCP offers. However, this is embarrassing to GCP that this isn’t easier. These were very basic requirements from this customer, yet so much rigmarole was needed to get it set up.

manigandham 7y ago
Multi-cluster global load balancing isn't "very basic" and no other cloud is any easier. AWS requires stacking the Global Accelerator on top of their ALB/ELBs but doesn't have smart routing across clusters and Azure only has Frontdoor which requires completely manual setup and has no backend integration.
- ec109685 7y ago
  Deploying an app to more than one geographic region on earth should be very basic. For mostly read only sites, it is mean to make your users suffer extra latency and your reliability goes down. The authors had to go read source code to figure out obscure annotations at one point to get container aware networking to work, which then wasn’t compatible with Google’s tools to setup global ingress.
  - manigandham 7y ago
    That isn't very basic and never has been. If it's just a read-only site then all you need is a CDN, not load balancing with multiple regions running Kubernetes clusters. What other cloud vendor or PaaS offers this? The only one that has seamless global deployment is Cloudflare's Workers but that's limited to Javascript code in a lightweight functions environment.
    - ec109685 7y ago
      They are making one part of this easier at least: https://twitter.com/vicnastea/status/1232751949117702145?s=20 https://twitter.com/vicnastea/status/1232751949117702145?s=2...

manigandham 7y ago

They are product and feature names used by the GCP platform (and this article). It's perfectly accurate and descriptive.