<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cdn on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/cdn/</link><description>Recent content in Cdn on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Mon, 01 Jun 2020 09:35:07 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/cdn/index.xml" rel="self" type="application/rss+xml"/><item><title>Why You Shouldn’t Use AWS S3 or CloudFront to Deliver Static Assets</title><link>http://karpoke.ignaciocano.com/2020/06/01/why-you-shouldnt-use-aws-s3-or-cloudfront-to-deliver-static-assets/</link><pubDate>Mon, 01 Jun 2020 09:35:07 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/06/01/why-you-shouldnt-use-aws-s3-or-cloudfront-to-deliver-static-assets/</guid><description>&lt;blockquote&gt;
&lt;p&gt;By Mehul Mohan AWS is THE cool kid in the town. Every comparison of
different cloud providers is incomplete unless you compare them with AWS
at least once. But S3, the most popular solution for storing on the
cloud and the one everyone loves, should&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» freeCodeCamp.org | &lt;a href="https://www.freecodecamp.org/news/do-not-use-s3-for-static-assets/"&gt;freecodecamp.org&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>