<?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>Global on Blog of Christian Felde</title><link>https://blog.cfelde.com/tags/global/</link><description>Recent content in Global on Blog of Christian Felde</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 20 Dec 2017 13:22:28 +0000</lastBuildDate><atom:link href="https://blog.cfelde.com/tags/global/index.xml" rel="self" type="application/rss+xml"/><item><title>On edge architecture</title><link>https://blog.cfelde.com/2017/12/on-edge-architecture/</link><pubDate>Wed, 20 Dec 2017 13:22:28 +0000</pubDate><guid>https://blog.cfelde.com/2017/12/on-edge-architecture/</guid><description>&lt;p&gt;We’ve long had content delivery networks (CDN), that help speed up and reduce latency for your web visitors. This works by making sure that the CDN has servers that are physically closer and on a better network connection (fewer hops) compared to where your visitor is based. You maintain multiple copies of the same content spread out around the world, just to ensure you stay close to where your users are.&lt;/p&gt;</description></item></channel></rss>