AWS is an API. Anybody who does not realize or can not exploit this fact this pays massive premiums for using it (probably a lot of businesses which should have no business using AWS directly).
The application tooling is extra. And as far as I can tell, AWS is the only major public cloud that has decent coverage by tools of any flavour against their API, and they have the most decent set of language SDKs available. I am not familiar with GCP but anything Azure puts on the table is a catastrophe when compared to the ease of using boto3 to get a certain flow working.
Admittedly, their console has some defects it ought not to have, but with some systems and software development knowledge, you can grok all of the tooling AWS releases pretty easily.
The biggest of my problems with AWS that besides their API, some of their managed services are just not on the quality level as their core services (ec2, s3, ...).
GCP is pretty pleasant overall. The API, command line, and UI are all pretty good. Vast majority of functionality is supported in all three places too. Like all providers, they have a few services that suck but overall Google has done a great job at developer experience.
> AWS is an API. Anybody who does not realize or can not exploit this fact this pays massive premiums for using it (probably a lot of businesses which should have no business using AWS directly).
It's a freaking huge API and all of us would suck a little bit more of it without tooling around it.
Most of my grief is wrestling with the misc tools which obfuscate the underlying API. Bad or good design aside, I just need to see what's on the wire. Once I kinda grok the mechanics, I can map whatever tool's (terrible) UX to the reality.
It's my mental quirk. Maybe the inability to suspend disbelief. It's always slowed me down. But once I have a mental model, I can move pretty fast.
AWS's core is developer experience.
AWS is an API. Anybody who does not realize or can not exploit this fact this pays massive premiums for using it (probably a lot of businesses which should have no business using AWS directly).
The application tooling is extra. And as far as I can tell, AWS is the only major public cloud that has decent coverage by tools of any flavour against their API, and they have the most decent set of language SDKs available. I am not familiar with GCP but anything Azure puts on the table is a catastrophe when compared to the ease of using boto3 to get a certain flow working.
Admittedly, their console has some defects it ought not to have, but with some systems and software development knowledge, you can grok all of the tooling AWS releases pretty easily.
The biggest of my problems with AWS that besides their API, some of their managed services are just not on the quality level as their core services (ec2, s3, ...).