3 ms·
> I'm trying it... starting to have second thoughts though. They make it look like it's all ready to go and then you start uncovering bits and pieces of things
by outworlder 8y ago
> I'm trying it... starting to have second thoughts though. They make it look like it's all ready to go and then you start uncovering bits and pieces of things that seem to be half-done, half-legacy, half-dead at the same time. TBH it looks like they got spread too thin and can see how a good amount of services are solid while many are just there.
Interestingly, that's my experience on Azure. Seems like a lot of offerings were smashed together in order to try to form a coherent product.
- ams6110 8y agoSeems like a lot of offerings were smashed together in order to try to form a coherent product. Seems like that would apply to many, many web services and products in the last decade.
- outworlder 8y agoTrue. But even the worst AWS offerings ahemEKSahem are still integrated across the product line. You can expect easy integration with other AWS services. And indeed what little it offers, it's integrated (AWS AutoScaling groups, NLBs, IAM, etc) Azure's AKS is way better as a whole, but until recently, wasn't integrated with their own scalesets. How does that even happen? To be fair to Azure, AKS is an example on how to rollout features. All the knobs are there (even more so than GKE, you can even set cluster ip ranges), it just works and no silly surprises. At least, I haven't found surprising behavior yet.