<story><title>Cloudflare&apos;s Disruption</title><url>https://stratechery.com/2021/cloudflares-disruption/</url></story><parent_chain><item><author>jerf</author><text>&amp;quot;More importantly, AWS itself is locked-in to its integrated approach: the entire service is architected both technically and economically to be an all-encompassing offering; to modularize itself in response to Cloudflare would be suicidal.&amp;quot;&lt;p&gt;Eh, somewhat. AWS is already modular in a lot of ways. You want S3? You got it, no matter where you are. (We&amp;#x27;re talking after them doing some sort of fee drop here.) You want to run exactly one EC2 instance? No problem. You want a message queue? You don&amp;#x27;t &lt;i&gt;need&lt;/i&gt; anything else. You can integrate it with the notification service but it&amp;#x27;s optional.&lt;p&gt;Sure, some of their services are integrated, but a lot of that integration is just &amp;quot;this service pulls from S3 and writes to S3&amp;quot;, not massive integration at every level.&lt;p&gt;There is some stuff that is deeply tied in, yeah. But it&amp;#x27;s not like every single AWS service is deeply tied into half the other ones and the moment you open an EC2 instance you also are buying into a dozen other services. (It may feel like it if you put together a network and override the default block storage, but that&amp;#x27;s really just giving you knobs that are simply preset elsewhere, not really &amp;quot;lockin&amp;quot;.) A lot of it is already pretty modular.</text></item></parent_chain><comment><author>Jonovono</author><text>I think you are missing the point. AWS is modular WITHIN AWS. It&amp;#x27;s not a decentralised modular system. ie, it can&amp;#x27;t play well with existing companies because of the hefty egress prices they charge. The point in the article is that, maybe, if you take away the egress fees that opens up a new world where services of different companies can play together nicely (instead of waiting for AWS to implement something), and that creates a new form of innovation that we can&amp;#x27;t quite predict that could possibly compete with AWS</text></comment>
<story><title>Cloudflare&apos;s Disruption</title><url>https://stratechery.com/2021/cloudflares-disruption/</url></story><parent_chain><item><author>jerf</author><text>&amp;quot;More importantly, AWS itself is locked-in to its integrated approach: the entire service is architected both technically and economically to be an all-encompassing offering; to modularize itself in response to Cloudflare would be suicidal.&amp;quot;&lt;p&gt;Eh, somewhat. AWS is already modular in a lot of ways. You want S3? You got it, no matter where you are. (We&amp;#x27;re talking after them doing some sort of fee drop here.) You want to run exactly one EC2 instance? No problem. You want a message queue? You don&amp;#x27;t &lt;i&gt;need&lt;/i&gt; anything else. You can integrate it with the notification service but it&amp;#x27;s optional.&lt;p&gt;Sure, some of their services are integrated, but a lot of that integration is just &amp;quot;this service pulls from S3 and writes to S3&amp;quot;, not massive integration at every level.&lt;p&gt;There is some stuff that is deeply tied in, yeah. But it&amp;#x27;s not like every single AWS service is deeply tied into half the other ones and the moment you open an EC2 instance you also are buying into a dozen other services. (It may feel like it if you put together a network and override the default block storage, but that&amp;#x27;s really just giving you knobs that are simply preset elsewhere, not really &amp;quot;lockin&amp;quot;.) A lot of it is already pretty modular.</text></item></parent_chain><comment><author>H8crilA</author><text>You forgot about the egress fees. Try running BigQuery on a (big) dataset stored in S3. You probably wouldn&amp;#x27;t even think of that because of how stupid that is at the moment.</text></comment>