dorian taylor

A couple weeks ago I wrote a newsletter (https://buttondown.com/dorian/archive/what-do-you-do-when-a-piece-of-your-stack-goes-bad/) about the risks peculiar to vendors of software and information services, and lo and behold, AWS (and everything running on top of it) goes down for several hours. I checked and it turns out this actually happens on the order of about twice a year. Seems like a it'd be valuable differentiator to be the guy who's still running when AWS is down. I'm taking free introductory calls to talk about this and similar matters: https://methodandstructure.com/30-minute-call . See other services at https://methodandstructure.com/ . • where I got the stat from: https://statusgator.com/blog/aws-outage-history/ • the CrowdStrike incident: https://en.wikipedia.org/wiki/2024_CrowdStrike-related_IT_outages 00:00 - aws fall down go boom 00:54 - part of what you're paying for is the uptime 01:21 - but the platform makes it hard to leave 02:08 - what if you had to drop a vendor in a hurry? 03:00 - determine switching costs before you buy 04:00 - this analysis is something i can do for you 05:28 - i've opened my calendar for calls