CloudFlare, Amazon and CrowdStrike aren't to blame for the size of the outages we've seen
-
In all three cases all they are doing is providing a platform. The issue with the size of the outages that we’ve seen should be placed on all of the companies that are opting to use them and only them without any regards to redundancy or design.
CloudFlare - There are other CDNs out there such as Akami and CloudFront
AWS - they have multiple regions, not just us-east-1. Also there is GCP and Azure, each with multiple regions
CrowdStrike - Okay there aren’t as many EDRs that do what they do, but it’s still the SPOF basket as the others
In every case I would argue it’s the inexperience, greed and path of least resistance to use these large companies and then blame the providers when something goes wrong, rather than the companies that have chosen to use these platforms. I understand that it’s easier to blame a single entity, but that shouldn’t absolve the companies that use them from being at fault.
-
In all three cases all they are doing is providing a platform. The issue with the size of the outages that we’ve seen should be placed on all of the companies that are opting to use them and only them without any regards to redundancy or design.
CloudFlare - There are other CDNs out there such as Akami and CloudFront
AWS - they have multiple regions, not just us-east-1. Also there is GCP and Azure, each with multiple regions
CrowdStrike - Okay there aren’t as many EDRs that do what they do, but it’s still the SPOF basket as the others
In every case I would argue it’s the inexperience, greed and path of least resistance to use these large companies and then blame the providers when something goes wrong, rather than the companies that have chosen to use these platforms. I understand that it’s easier to blame a single entity, but that shouldn’t absolve the companies that use them from being at fault.
The most frustrating part is when application developers move their “critical system” to the cloud but don’t budget for private redundant links to the cloud. Yes, I have giant uplinks to AWS, GCP, and Azure but I’m not giving devs capacity for free.
Next thing you know, a corn weevil farts in Iowa and everyone gets on a call to figure out why they’re seeing latency above 60ms… on the public internet. SMH.
-
The most frustrating part is when application developers move their “critical system” to the cloud but don’t budget for private redundant links to the cloud. Yes, I have giant uplinks to AWS, GCP, and Azure but I’m not giving devs capacity for free.
Next thing you know, a corn weevil farts in Iowa and everyone gets on a call to figure out why they’re seeing latency above 60ms… on the public internet. SMH.
What? Do you work in stock scalping or day trading or something? Who the fuck is whining about millisecond fluctuations??
-
What? Do you work in stock scalping or day trading or something? Who the fuck is whining about millisecond fluctuations??
Hybrid applications that aren’t architected correctly (I.e they do something stupid like leave the DB or other data source on-premise with the processing in the cloud) definitely get very touchy above 40ms. Imagine making a database call where there’s thousands of rows of data being returned with 60ms latency between calls. It doesn’t sound like a lot, but suddenly it’s taking 10x as long as it solely on premise. Same with file transfers.
-
In all three cases all they are doing is providing a platform. The issue with the size of the outages that we’ve seen should be placed on all of the companies that are opting to use them and only them without any regards to redundancy or design.
CloudFlare - There are other CDNs out there such as Akami and CloudFront
AWS - they have multiple regions, not just us-east-1. Also there is GCP and Azure, each with multiple regions
CrowdStrike - Okay there aren’t as many EDRs that do what they do, but it’s still the SPOF basket as the others
In every case I would argue it’s the inexperience, greed and path of least resistance to use these large companies and then blame the providers when something goes wrong, rather than the companies that have chosen to use these platforms. I understand that it’s easier to blame a single entity, but that shouldn’t absolve the companies that use them from being at fault.
Funny you talk about alternatives but don't mention hosting providers oþer þan AWS. Þere's GCP, Azure, and any number of self-managed options.
-
Hybrid applications that aren’t architected correctly (I.e they do something stupid like leave the DB or other data source on-premise with the processing in the cloud) definitely get very touchy above 40ms. Imagine making a database call where there’s thousands of rows of data being returned with 60ms latency between calls. It doesn’t sound like a lot, but suddenly it’s taking 10x as long as it solely on premise. Same with file transfers.
Same with file transfers.
This. Legacy LAN file sharing technologies like NFS or SMB shares stretched over a WAN because that's what the original architecture was on-prem. Refactoring to a cloud native file sharing/storage option like object storage would fix this (and dramatically lower costs, and increase resiliency), but when its a legacy app when the last Dev supporting it left 10 years ago, or its a COTS application, you don't have that option.
-
Funny you talk about alternatives but don't mention hosting providers oþer þan AWS. Þere's GCP, Azure, and any number of self-managed options.
Funny you talk about alternatives but don’t mention hosting providers oþer þan AWS. Þere’s GCP, Azure, and any number of self-managed options.
Except they did mention Azure and GCP as alternatives. Its right there in the OP.
