I disagree. The only reason for AWS slow adoption of Kubernetes was because they couldn't find a strong use-case within their customer base. Customers knew they wanted to use it, but they really didn't know how or why it would be better than using other type of container architecture. AWS doesn't build services for customers to toy around. Every new service is a significant investment so the data and the use cases ne…
Bollocks! AWS has had few horses(i.e aws ECS) in this race so they waited to see if they can win. Obviously K8 wins over ECS so now they have no choice but embrace K8. The last thing Amazon wants is to be easy replaceable with a different provider. I guess this is same with the underdogs as well(i.e Google/Microsoft) and that's why they do all they can to lock you in with proprietary services(i.e Appengine, Datastore…
‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
11–20 of 112 posts
Re: ‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
#12Re: ‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
#13Earlier quoted context omitted.
Bollocks! AWS has had few horses(i.e aws ECS) in this race so they waited to see if they can win. Obviously K8 wins over ECS so now they have no choice but embrace K8. The last thing Amazon wants is to be easy replaceable with a different provider. I guess this is same with the underdogs as well(i.e Google/Microsoft) and that's why they do all they can to lock you in with proprietary services(i.e Appengine, Datastore…
I feel like this is quite a cynical view. Amazon and other cloud providers want to attract and keep users by providing the best product possible. This may come in different forms so some people want easy-to-setup databases (AWS RDS) others want auth (IAM) handled for them, others scalability (Appengine) or maybe email (SES). In order to create these services and to make life easier for those who want them, it may req…
I really find that assertion hard to believe. AWS is notoriously expensive and oddly enough its added value comes in the form of proprietary technologies which require non-transferable tech skills. The lock-in overload goes to the extreme of leading technicians to specialize exclusively in AWS services which leads to the infamous title of AWS engineer. This doesn't happen by chance, but by design. It's like a very expensive mousetrap designed to help victims get in but being practically very hard if not impossible to get out.
Re: ‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
#14"Hey we have this barely usable, rocket-science level complex, container orchestration tool. How about we make it available to everyone and make sure the message is that you can deploy anywhere? Get people to look at us as an alternative instead of AWS as the default, while using a tool built by us".
Of course AWS was not excited about supporting a tool that might make it easier to leave AWS.
Re: ‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
#15I disagree. The only reason for AWS slow adoption of Kubernetes was because they couldn't find a strong use-case within their customer base. Customers knew they wanted to use it, but they really didn't know how or why it would be better than using other type of container architecture. AWS doesn't build services for customers to toy around. Every new service is a significant investment so the data and the use cases ne…
AWS is implementing Kubernetes to make it easier for people who use it already to migrate to their service. It's the same reason all other cloud providers are doing so.
I can pretty much guarantee that the products Amazon introduces aren't designed to lock people in or make it hard to switch, it's to make it easy for them to start using AWS and not NEED to switch. They design products and their APIs to solve problems customers are facing. This is what everyone is doing.
Re: ‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
#16Could also be that they compare AWS vs. GCP, but I'd dont think so.
Re: ‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
#17I'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.
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).
At least this is my impression.
Re: ‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
#18I'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.
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).
Re: ‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
#19Re: ‘AWS vs. K8s’ Is the New ‘Windows vs. Linux’
#20Earlier quoted context omitted.
Bollocks! AWS has had few horses(i.e aws ECS) in this race so they waited to see if they can win. Obviously K8 wins over ECS so now they have no choice but embrace K8. The last thing Amazon wants is to be easy replaceable with a different provider. I guess this is same with the underdogs as well(i.e Google/Microsoft) and that's why they do all they can to lock you in with proprietary services(i.e Appengine, Datastore…
I feel like this is quite a cynical view. Amazon and other cloud providers want to attract and keep users by providing the best product possible. This may come in different forms so some people want easy-to-setup databases (AWS RDS) others want auth (IAM) handled for them, others scalability (Appengine) or maybe email (SES). In order to create these services and to make life easier for those who want them, it may req…
Google open sourced k8 so that they can get a pie from AWS and then lock you in with other proprietary services.