wparad

4 ms·

1.
by wparad 6mo ago
I really don't understand why everyone is jumping up and down over this. I doesn't really feel like a real solution. But I couldn't contain myself and wanted to a write a response: https://authress.io/knowledg
2.
by wparad 10mo ago
The point here is that, it's important to clarify what you mean by "untested code". Some companies release untested code all the time to production by hide their usage behind feature flags. They admit that the code has not be
3.
by wparad 10mo ago
Hmm, I never considered potentially using an SLA on latency as a potential way to justify the argument. If I pull this content into a future article or talk, I will definitely consider reframing it for easier understanding.
4.
by wparad 10mo ago
100%
5.
by wparad 10mo ago
Actually this isn't the only thing that exists. As I pointed out that only exists for resources that are duplicated between regions. There's also the critical fallbacks that exist at the service level to decide which resources to
6.
by wparad 10mo ago
:)
7.
by wparad 10mo ago
Thank you.
8.
by wparad 10mo ago
Ha, thanks, we'll fix that.
9.
by wparad 10mo ago
Thank you!
10.
by wparad 10mo ago
Absolutely, part of the problem is that a whole region being down is often less of a problem, then just one critical service. And as you point out the blast radius of a critical dependency is huge.
11.
by wparad 10mo ago
The sad truth of the world is that in many cases latency isn't the most critical aspect for tracking. We absolutely do track it because we have the expectation that authentication requests complete. But there are many moving parts to t
12.
by wparad 10mo ago
Hmmm, which part of the intro did you find an issue with? I want to see if I can fix it.
13.
by wparad 10mo ago
This is absolutely true, but the end result is the same. The assumption is "We can fix a third party component behaving temporarily incorrectly, and therefore we can do something about it". If the third party component never behav
14.
by wparad 10mo ago
In the last decade, there has been at least one time where we did issue credits to our customers when there was a problem. Issues credits back to our customers is a small compensation for any issue we're responsible for, and doing so i
15.
by wparad 10mo ago
Agreed, it is much too easy to fall into bad habits. The whole goal of OpenTofu is declarative infrastructure. With CDK and pulumi, it's very easy to end up in a place where you lose that. But if you need to do something in a particula
16.
by wparad 10mo ago
I think some people are going to scream when I say this, but we're using mostly CloudFormation templates. We don't use the CDK because it introduces complexity into the system. However to make CloudFormation usable, it is written
17.
by wparad 10mo ago
Thank you! One of the question I frequently get is "do you automatically rollback". And I have hide in the corner and say "not really". Often, if you knew a rollback would work, you probably could also have known to not
18.
by wparad 10mo ago
I think there are two worlds of thought to the "AWS is totally dead everywhere". And that's: * It is never going to happen due to the way AWS is designed (or at least told to us, which explains why it is so hard to execute ac
19.
by wparad 10mo ago
Maybe I should have titled the article "AWS Route53 HealthChecks are amazing" :)
20.
by wparad 10mo ago
Thank you!
21.
by wparad 10mo ago
I spent a long time, trying to figure out, what the title of the article, should be. I'm terrible at SEO and generating click-bait titles, it is unfortunately, what, it, is.
22.
by wparad 10mo ago
Good catch. The truth is, while we track downtime for incident reporting, it's much more correct to actually be tracking the number of requests that result in a failure. Our SLAs are based on request volume, and not specifically time.
23.
by wparad 10mo ago
It's a good point. We don't actually commit to running infrastructure in one specific AWS region. Customers can't request that the infra runs exactly in us-east-1, but they can request that it runs in "Eastern United Sta
24.
by wparad 10mo ago
If the check can't be done, then everything stays stable, so I'm guessing the question is, "What happens if Route 53 does the check and incorrectly reports the result?" In that case, no matter what we are using there is
25.
by wparad 10mo ago
Hey, I wrote that article! I'll try to add comments and answer questions where I can. - Warren
26.
by wparad 2y ago
That for sure is a great point, it's actually something Dorota brought up in her talk this year https://vimeo.com/940487124
27.
Breach – Enabling emergency data protection(medium.com)
1 points by wparad 6y ago|0 comments