Another "so close and yet so far away" release from AWS AWS needs to realize that: 1️⃣there's a world outside AWS 2️⃣not everybody has AWS' reliability requirements & profit margins This could've been awesome, but no, AWS keeps repeating the same mistakes https://pipelines.devops.aws.dev

To be fair, the Deployment Pipeline Reference Architecture (DPRA) gets *A LOT* of things right. Good job on that! Seriously 👏 I especially like all the examples! And there's a big need for something like this. I applaud AWS tackling this! But then problems starts to appear...

Announcing the return of office hours — now in a paid, 1-hour format! For 1000€, you can get my thoughts on any problem and actionable solutions for your company. No more strategic blunders! https://office-hours.vladionescu.me

I used to do this a lot in the past: folks reached out to get my thoughts over DMs/email and we'd schedule something. Due to a bunch of abuse I was forced to stop 😞 I missed them A LOT, so paid office hours is my attempt at bringing this back! We'll see how it goes 🤞

As an ECS on Fargate fan, I got a lot of questions about the recent incident / outage. Let's talk about it... 🧵 1/43 TL;DR: meh. Incidents happen and this one did not teach us anything new about building on AWS. I expect more profound drama during these roaring 20s!

Disclaimer: everything fails all the time! I view incidents as "normal" and this thread reflects that. Yes, AWS had incidents. Yes, us-east-1 is HUGE so it gets interesting incidents. Yes, AWS is bad at communication. This is the default and well-known state!

The thoughts in the quoted thread ruffled some feathers, so let's do a quick observability 101. Alternative title: "how to not get abused by your logging/ monitoring/ o11y vendor" A 30-tweet thread cause I am trying to micro-blog 👇 https://twitter.com/iamvlaaaaaaad/status/1543892406969442304

If you speak Romanian, I already gave a talk on this topic at Bucharest's Cloud Native Meetup in September 2021! See this video, starting at 51:05: https://youtu.be/XFP1-45ZL08?t=3065 Watch that instead, as this thread is an English re-cap of that talk!

Let's see how Amazon CodeWhisperer and GitHub Copilot compare! CodeWhisperer: in preview, just announced. Python, Java, JS Copilot: generally available, just graduated from preview. Dozens of languages(?) I'll compare a couple scenarios, but let me know if you have test ideas👇

Rant: can we please stop pretending that serverless in 2022 is the same thing as serverless in 2016? We're intellectually masturbating about what "serverless" means and we're confusing people, all while we're like on serverless v3! Of course v3 products don't fit in v1 boxes!

TL;DR: Serverless v1 came in with a bang but failed to capture most of the market. Serverless v2 is an effort to apply serverless practices to things most people already know and do, but "it's nOt TruE sERvErLeSs". At the same time, Serverless v3 is exploring what's next.

Brave: you're hiring and your process includes a coding quiz/take-home exercise Really brave: you're doing the above and assuming everybody has a dev env with 15 specific tools and DBs already installed, configured, and working perfectly "SWE candidates are so bad these days"🙄

What's the fastest way to scale containers on AWS in 2022? Is EKS faster than ECS? What's faster: serverless workers (Fargate) or to serverful workers (EC2)? What about App Runner and Lambda? Now we know: https://www.vladionescu.me/posts/scaling-containers-on-aws-in-2022

Old: Ops does things by hand, takes forever, slows down companies. Idea: Ops can use code to automate things and work closer with Dev to speed things up! Dev will optimize for easier Ops too. Fked up now: DEVS MUST ALSO WRITE TERRAFORM AND LEARN EVERYTHING ABOUT KUBERNETES!

AWS: repeatedly punches you in the face. Also AWS: here’s AWS Helmet, so taking those punches is easier. Yay, we’re customer obsessed! Bias for action! Don’t get me wrong, the helmets are awesome. But they should not be needed! With scale comes responsibility, and all that.