3 ms·
Thanks a lot for taking time to respond. I've a couple of clarifying questions: > Two reasons really, the first is that AWS has become this bloated mess of "st
by ignoramous 10y ago
Thanks a lot for taking time to respond. I've a couple of clarifying questions:
> Two reasons really, the first is that AWS has become this bloated mess of "stuff", making it increasingly harder to use
Are you referring to any specific offerings: CodeDeploy/Beanstalk/EC2? Or generally the entirety of AWS catalog? I agree that the sheer amount of configurations and the breath of offerings might appear bloated and there are parts where AWS looks its age, not necessarily a bad thing, though.
> because so much time is needed to either constantly look at it to see what's new/changed or vigilantly document everything
I am not able to relate to this. AWS is pretty serious abt backwards compatibility and making transitions smooth unless there's a serious security risk.
Re: Console:
This complaint comes up often on HN. Thanks for pointing it out.
Re: Convention over configuration:
K8s seems to be a great piece of software from what I keep reading abt it. I can understand why anyone would choose to use it. I am left wondering why it isn't as easily usable on AWS infrastructure... I guess I must try it out myself, someday.
- tzaman 10y agoI'm not referring to any specific offering, but just the sheer amount of ways to accomplish things on AWS - and the docs don't help, I urge you to compare (or even time) the process of following the docs in setting up AWS versus GKE clusters. You'll notice the process is much faster with GKE, especially because the docs include at least some real-world examples, compared to AWS where the documentation is almost completely abstract. And as a "very" curious developer, I always get pulled into analysis paralysis. Not so with GKE. There's one way to accomplish a particular thing, the only choice is UI versus CLI - and since most of us have Google accounts anyway, gettings started with GKE is maybe a couple of commands and you have a cluster up and running. Try googling how to set up Jenkins/WordPress on AWS/GKE. A VERY real world examples and Google provides docs, AWS does not - I'm not interested in high-level overviews, I want to solve a particular problem. What AWS needs first and foremost is a competent UX team.
- ranman 10y agoIs something like this useful for you? https://aws.amazon.com/getting-started/tutorials/ https://aws.amazon.com/getting-started/tutorials/
- tzaman 10y agoNope, but it illustrates my points perfectly. A company like Amazon should have hundreds of those, with real use cases that developers (or DevOps) care about. For instance, I have a Rails/Node/Go/whatever app. How do I deploy it using any of the available services? Which one is preferred? Why? What about the connecting services, like Postgres+Redis? (I know there's an offering for everything, I'd like to know how it all fits together, best practices, etc)
- ignoramous 10y agoMakes sense. Thanks once again. :)