3 ms·

i’ve built bespoke automation at the api level for azure, gcp, and aws. using azure makes you want to watch the world burn. using gcp makes you want to give a

i’ve built bespoke automation at the api level for azure, gcp, and aws. using azure makes you want to watch the world burn. using gcp makes you want to give alcoholism a fair try. using aws makes you wonder why we can’t have nice things. ime those who prefer gcp tend to use a web interface. those who don’t have a preference tend to use iac. you want to work directly with the api, for innumerable reasons. aws is the canonical example of use boring tech. nobody cares which database you use, not even a little. if you’re talking about your stack choices, your product likely has negative value. of all the projects i pull into my rss reader, github commits on the aws-go-sdk-v1 are the most consistent and unsurprising. ive been following aws api and service changes since boto1. there’s a lot i wish was different about aws, but nothing that’s urgent. someday we’ll get better providers. it won’t be azure or gcp. it will be a new player. by 2030 i’d expect to see someone disrupting aws by offering api compatible clones of the core services without egress fees. r53, dynamo, ec2, ec2 spot, lambda, s3, apigateway, sqs.

catlover76 3y ago
I defer to your expertise, esp when it comes to actually using these different services at scale, but as someone who used to deploy only to Heroku and wanted to learn real cloud deployment, AWS was pretty unapproachable. I almost laughed out loud at how unnecessarily arcane and difficult they made things when all I wanted to do was set up a simple Python app on EC2. Google Cloud felt easier and intuitive to get started with, so that's what I use now.
- nathants 3y ago
  too much maybe? yelling at clouds just feels so good sometimes. apologies. i do actually wish we could have nice things. this is how aws became easy and fun for me[1]. a similar interface could exist for any provider. heroku is right about picking the good parts and exposing only that as an interface. 1. https://github.com/nathants/libaws https://github.com/nathants/libaws
  - MrBuddyCasino 3y ago
    Thats sounds sweet. I suppose its just for when you really love lambdas (I don't)?
    - nathants 3y ago
      consider lambdas for managing ec2 spot instances, and other low volume tasks.
  - catlover76 3y ago
    Cool, I'll check it out, thanks

catlover76 3y ago

I defer to your expertise, esp when it comes to actually using these different services at scale, but as someone who used to deploy only to Heroku and wanted to learn real cloud deployment, AWS was pretty unapproachable. I almost laughed out loud at how unnecessarily arcane and difficult they made things when all I wanted to do was set up a simple Python app on EC2. Google Cloud felt easier and intuitive to get started with, so that's what I use now.

nathants 3y ago
too much maybe? yelling at clouds just feels so good sometimes. apologies. i do actually wish we could have nice things. this is how aws became easy and fun for me[1]. a similar interface could exist for any provider. heroku is right about picking the good parts and exposing only that as an interface. 1. https://github.com/nathants/libaws https://github.com/nathants/libaws
- MrBuddyCasino 3y ago
  Thats sounds sweet. I suppose its just for when you really love lambdas (I don't)?
  - nathants 3y ago
    consider lambdas for managing ec2 spot instances, and other low volume tasks.
- catlover76 3y ago
  Cool, I'll check it out, thanks