[_fat_santa]

> There’s also just no consistency in the platform - the CLI for instance has totally different flags and names depending on which sub command you’re using. It’s like this everywhere in Azure.

For all of AWS's faults, one of the reason I really like them is how consistent everything is. There were so many instances where I could correctly guess the right command for the AWS CLI based on how other services worked, I could never do that with GCP or Azure.

I would love to read an article about how AWS ensures this kind of consistency. Given how Azure and GCP both messed this up, it's clearly not a trivial problem (even though it may seem like one)

[dabbz]

They have a governance panel for all AWS services that approves design docs and API contracts (at least this is what I was told by an old manager who worked on AWS back in the day).

[patch_cable]

It isn't quite as formal as that, but there is a group of engineers who review new APIs for following AWS-wide standards.

[dastbe]

there's also a significant amount of automation in place these days to sass you in the right direction, i.e.

* focusing on resources and operations on resources

* using consistent and expected naming schemes, pluralization, etc.

it also helps that the sdks and clis are very raw wrappers around this, such that if you know what it looks like in the sdk then it will look similar in the cli.