3 ms·
That just means it takes longer to test. It may not be possible to do it in a reasonable timeframe with the volumes involved, but if you already have 100k serve
by Aeolun 11mo ago
That just means it takes longer to test. It may not be possible to do it in a reasonable timeframe with the volumes involved, but if you already have 100k servers running to serve 25M requests per second, maybe briefly booting up another 100k isn’t going to be the end of the world?
Either way, you don’t need to do it on every commit, just often enough that you catch these kinds of issues before they go to prod.
- mewpmewp2 11mo agoBut they are probably doing hundreds of deployments a day, so that would make their pipelines extremely long? Not to mention costs.
- tatersolid 11mo ago> maybe briefly booting up another 100k isn’t going to be the end of the world Cloudflare doesn’t run in AWS. They are a cloud provider themselves and mostly run on bare metal. Where would these extra 100k physical servers come from?
- Aeolun 11mo agoFrom their desire to representatively test before they deploy to production? Doing stuff at scale doesn’t suddenly mean you skip testing. And just because they host stuff themselves doesn’t mean they couldn’t run on the cloud if they needed to.
- mewpmewp2 11mo agoCloudflare infra costs are probably 300 mil+ usd. Their gaap profit is negative, their non gaap income is less than their infra expenses. Can you imagine how much they would have to charge more or spend more if they had to duplicate or simulate their production environment in staging and for each of the 100s deployments they probably do a day? Their main cost of revenue is these infra costs.