Hacker News Reader

Comment by newaccoutnas | Hacker News Reader

I'm not really following, perhaps it's too early here. AWS is a cloud provider, Kubernetes is container orchestration software. Here's a crazy thing, we do K8S on AWS.

View on HN

K8S is the commoditization of of Amazon's compute infrastructure. This standardizes it and makes it easier to switch and to build vendor independent tooling around it. Of course the strategy of AWS now at least be the first two parts of the old Microsoft strategy with regards to open standards: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis... (Hopefully not the third part.)

There is still lots that Amazon does that is unique and proprietary. And it has tons of respect in the industry.

But as more becomes standardized on Kubernetes and more becomes automated via Service Providers, it will make further commoditize the market.

Google needs to do the following: - Better CDN that can work with any origin. - Work hard on getting Service Providers/Service Catalog into Kubernetes with all the latest Google Services (it is very patchy support at the moment.) - Buy Gitlab and support the shit out of it -- that is one great product.

IDK about Gitlab. Google has the worse reputation about keeping products alive. That reputation along with the privacy reputation is going to drive adopters away, especially the ones who are not using GitHub because of Microsoft.

I think the comparison that the author makes is that AWS and Kubernetes are both platforms that you code your apps to, just like Windows and Linux

Even more crazy, you can put Linux on Windows!

If you take a step away from the spiral that is AWS PaaS / SaaS services, k8s isn't that dissimilar to EC2, VPC, EBS, and IAM and thus a lot of the same arguments around lock-in apply.

This will become more obvious as people put windows VMs on k8s because it's there and they can.

That's using AWS as a VM and VPC provider. AWS don't want you to do that, or at least, that's not how they'd like you to use their services (IMO).

I think it's pretty clear that AWS is happy for you to use their services in all manner of ways, using heavy AWS-proprietary services or not. Nothing wrong particular with "lift-and-ship" as they call it when you migrate on on-prem app mostly unchanged.

At least this is my impression.

Of course they would love for you to do a lifts and shift, it makes them more money than if you are “cloud native”.

The article sounds like a comparison of buzzwords tailored for the technically challenged. I mean, I'm pretty sure that a Dilbert strip will be created based on the reaction of the pointy haired boss to this specific article.

Exactly! This looks like an apples vs. oranges comparison.

It's apple corer vs. fruit basket.

Reply on news.ycombinator.com