
Jun 5, 2026 · 1 hr 5 min · 17 segments
Share Episode Welcome back to another hopefully, relief from architectural existential…
Seth EliotGuestWarrenHostSo you're saying it's kind of chaotic out there for folks running software in the cloud, huh? I have to really wonder, is it different than it's always been? Or are we just more in tune? Is it more public? We start to see those things.
It's all about whatever makes a good news story.
I've spent a decade telling folks it's a mess out there.

And I don't want to scare them, but they have to take precautions, right? If you're going to go out hurricane chasing, you better have the right equipment.

If you're going to launch software in the world, whether it's a cloud or a data center, You got to be building for resilience.

I guess the biggest mistake people make is when they move to the cloud, they think, all right, I'm done.

When I was at AWS, I was fortunate enough to actually co-author the shared responsibility model for resilience.

But we did heavily crib off of the shared responsibility model for security, which predated us by quite a few years, took the same diagram and everything, just replaced the text.
Well, I think this is where in a lot of different areas of academia, we see the same thing repeated over and over again, but with slightly different words.
But the mental model usually remains the same.
But the question I'm going to ask you is when you say resilience, what exactly do you mean?

Yeah, it is a little hot topic and apologies to people that I don't give the definition they want to hear right now.

But it's really the ability to either maintain availability or recover from faults and get back to availability when those bad things happen, right? And when those bad things are happening in the cloud or in your server under your desk, right? How do you tolerate that and how do you recover from that?
I feel like that's the uncontroversial definition.
It's not as controversial.
I don't know
There is a particular Slack channel I'm in that
So you're saying it's kind of chaotic out there for folks running software in the cloud, huh? I have to really wonder, is it different than it's always been? Or are we just more in tune? Is it more public? We start to see those things.
It's all about whatever makes a good news story.
I've spent a decade telling folks it's a mess out there.

And I don't want to scare them, but they have to take precautions, right? If you're going to go out hurricane chasing, you better have the right equipment.

If you're going to launch software in the world, whether it's a cloud or a data center, You got to be building for resilience.

I guess the biggest mistake people make is when they move to the cloud, they think, all right, I'm done.

When I was at AWS, I was fortunate enough to actually co-author the shared responsibility model for resilience.

But we did heavily crib off of the shared responsibility model for security, which predated us by quite a few years, took the same diagram and everything, just replaced the text.
Well, I think this is where in a lot of different areas of academia, we see the same thing repeated over and over again, but with slightly different words.
But the mental model usually remains the same.
But the question I'm going to ask you is when you say resilience, what exactly do you mean?

Yeah, it is a little hot topic and apologies to people that I don't give the definition they want to hear right now.

But it's really the ability to either maintain availability or recover from faults and get back to availability when those bad things happen, right? And when those bad things are happening in the cloud or in your server under your desk, right? How do you tolerate that and how do you recover from that?
I feel like that's the uncontroversial definition.
It's not as controversial.
I don't know
There is a particular Slack channel I'm in that
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.