Building a Simple Content Delivery Network

@brendan

http://au.marsupial.graphics

571 ms

OH NO! IT’S SLOWWWWW!

But why?

10,093 miles one way

20,186 miles roundtrip

152 ms roundtrip

10,093 miles: 76 ms

267 ms roundtrip

Anatomy of a web request

DNS Query TCP Connection HTTP Request

DNS Query TCP Connection HTTP Request SYN ACK SYN-ACK CLIENT
SERVER

DNS Query TCP Connection HTTP Request

DNS Query TCP Connection HTTP Request 2 Round Trips 267
ms * 2 = 534 ms

DNS Query TCP Connection SSL Channel HTTP Request CLIENT HELLO
SERVER HELLO CLIENT SERVER CLIENT KEY CHANGE CIPHER

DNS Query TCP Connection SSL Channel HTTP Request 4 Round
Trips 267 ms * 4 = 1,068 ms

<html> <head> <title>This is typical</title> <script src=“http://here.com/jquery.js”></script> <script src=“http://there.com/underscore.js”></script> <script
src=“http://everywhere.com/angular.js”></script> <script src=“http://somewhere.com/emoji.js”></script> <script src=“http://nowhere.com/analytics.js”></script> </head> <body> <h1>This is a web page!</h1> </body> </html>

1. Get HTML page

1. Get HTML page 2. Get assets (scripts, stylesheets, images)

HTTP: 4 round trips = 1,064 ms

HTTP: 4 round trips = 1,064 ms HTTPS: 8 round trips = 2,128 ms!

Now what?

Content Delivery Network

ORIGIN CACHE USER

The Cache Server

ORIGIN CACHE

DNS Rules!

ORIGIN CACHE USER USER

ORIGIN CACHE USER USER From London us.marsupial.graphics

ORIGIN CACHE USER USER From London

ORIGIN USER From Hong Kong

571 ms → 32 ms 18x FASTER!

Building a Simple Content Delivery Network

Building a Simple Content Delivery Network

More Decks by Brendan Schwartz

Other Decks in Technology

Featured

Transcript