Cloudflare Cache Reserve Walkthrough and Demo

00:00

hello my name is humir Ahmed and in this

00:02

video I'm going to walk through Cloud

00:03

for cash reserve and follow up with demo

00:06

I will very briefly discuss some Basics

00:08

from cloud for CDN before getting right

00:10

into Cash Reserve to provide a better

00:12

grasp of how everything fits together

00:14

however I'll keep this very minimal so I

00:16

can focus on cash Reserve for more

00:19

thorough understanding of cloud

00:20

vercidian in general and how it works

00:22

please see the cloud for CDN reference

00:24

architecture in the prior video I did on

00:26

cloudflare CDN walkthrough with that

00:29

let's get going

00:31

first let's talk about how easily you

00:33

can get started and onboarded onto

00:34

cloudflare CDN

00:36

from the dashboard simply click add site

00:38

and enter your domain cloud4 can

00:41

automatically import your DNS records

00:43

from your existing DNS provider and

00:46

finally you're given Cloud for name

00:47

servers you can use to change your

00:49

authoritative DNS so here you're using

00:51

cloudford's DNS Azure authoritative DNS

00:54

and also onboarded onto cloudflare CDN

00:58

now if you don't want to change your

01:00

primary or authoritative DNS you can

01:02

still use cloudflare CDN by simply doing

01:05

a partial cname setup so lots of

01:07

flexibility there

01:10

so if we look at the very basics of the

01:12

traffic flow now first HTTP request is

01:15

made closest data center to user handles

01:19

the request users HTTP request URL is

01:22

matched against the list of cachable

01:24

file extensions if the request matches

01:27

an extension on the list Cloud first

01:28

serves the resource from Cache if

01:30

present

01:31

second content is fetched from Cache or

01:34

origin cloudflare examines its caches in

01:37

multiple Network locations for content

01:39

and serves it if present if the content

01:42

is still in Quad verse cache cloudfare

01:44

attempts to revalidate the content with

01:45

the origin before serving the response

01:47

to the client if the resource is not

01:50

present in the cache Cloud Fair requests

01:52

the resource from the origin to fill the

01:53

cache and the response is then sent to

01:55

the client who initiated the request

01:59

if cachable content is cached on the

02:01

response so cloudflare's cash logic

02:04

examines the HTTP response received from

02:07

the origin the response is either deemed

02:09

cachable and written to disk for use

02:10

with the next request for the same

02:12

resource or the request is deemed

02:14

uncashable

02:17

now let's take a look at the traffic

02:19

flow with Cloud Fair tiered cache with

02:21

smart tiered cache topology enabled as a

02:24

reminder tiered cash divides

02:26

cloudflare's network of global data

02:28

centers into a hierarchy of upper tiers

02:30

and lower tiers and in order to control

02:32

bandwidth number of connections between

02:34

an origin and cloudflare only upper

02:37

tiers are permitted to request content

02:39

from an origin and are responsible for

02:41

Distributing information to the lower

02:43

tiers smart tiered cash topology is the

02:46

default topology and available for free

02:48

for all plans this is also recommended

02:50

for most deployments instructing

02:52

cloudflare to find the single best upper

02:54

tiers for your Origins

02:56

benefits here include improved bandwidth

02:59

efficiency reduced origin load and

03:01

making websites more cost effective to

03:03

operate

03:04

so when client one sends a request to

03:06

the closest data center data center one

03:08

here

03:09

if the content is not cached the upper

03:11

tier data center label data center 3

03:13

here is checked if the content is not

03:16

cached at the upper tier the upper tier

03:17

requests the content from the origin

03:19

once their sponsors returned from the

03:22

origin the upper tier caches it and

03:24

returns a response to the lower tier

03:25

which also caches it and returns a

03:28

response to the client

03:30

now let's say client 2 makes the same

03:32

request for the same content to its

03:34

closest data center data center too

03:37

if the content is not cached to Data

03:39

Center too similar to Prior the upper

03:41

tier data center is checked however in

03:44

this case content was requested prior

03:46

via client 1 and the upper tier data

03:48

center has the content cached and

03:50

Returns the cache content to the lower

03:52

tier data center data center 2 which in

03:55

turn caches the content and responds

03:57

back to the client decreasing latency

03:59

saving bandwidth and load on the server

04:01

and providing better overall performance

04:05

so now that we have a better

04:07

understanding of cloud for CDN when does

04:09

a cache Miss occur well we have two

04:11

scenarios first intentional cash TTL

04:15

expired or content purged customers set

04:18

cache control time to signify when the

04:20

content is out of date and needs to be

04:22

revalidated once expired content needs

04:25

to be revalidated and may need to be

04:27

pulled from the origin if updated

04:28

version exists customers can Purge

04:31

content manually at any time

04:33

second unintentional cloudflare Purge

04:36

content due to lru or least recently

04:38

used algorithm to optimize storage less

04:41

frequently accessed content may be

04:43

purged based on lru or how long the

04:45

network wants content to remain cached

04:48

now this is where Cloud for cash Reserve

04:51

can be useful to further increase cash

04:53

hit ratio by automatically storing all

04:56

cachable files into cloudflare's

04:58

persistent object storage buckets

05:01

basically cash Reserve acts like an

05:03

ultimate upper tier and when there's a

05:05

cash Miss cloudflare will first check

05:07

these storage buckets before going to

05:09

the origin you can see here I've enabled

05:12

it and I'll walk through this more in

05:14

the demo

05:15

so let's look at the traffic flow now

05:18

again when the client sends a request to

05:20

the lower tier data center if the

05:22

content is not cached the upper tier

05:24

data center is checked this time however

05:26

if the content is not cached at the

05:28

upper tier the upper tier checks cash

05:30

Reserve instead of requesting straight

05:32

from the origin

05:33

if the content is not present in cash

05:35

Reserve cash Reserve will request it

05:37

from the origin once response is

05:40

returned from the origin cash Reserve

05:41

caches the content while replying to the

05:44

upper tier which also caches it and

05:46

Returns the response to the lower tier

05:48

which also caches it and responds to the

05:50

client now next time the same content is

05:53

requested if there is a cache Miss at

05:55

the lower tier data center the upper

05:57

tier data center is checked now if

05:59

there's say cache missed at the upper

06:01

tier data center let's say expired TTL

06:03

or content has been evicted cash Reserve

06:06

will be checked and if content exists at

06:08

Cash reserve it will be returned and

06:10

cached at the upper tier before being

06:12

returned and cashed at the lower tier

06:14

and returned to the client so you can

06:17

see here how cash Reserve acts as the

06:19

ultimate upper tier and minimizes the

06:21

need to pull from the origin decreasing

06:23

unnecessary egress fees

06:25

with that let's jump into the demo for

06:28

demonstration purposes I deployed a site

06:30

here that's basically a large image and

06:32

video gallery for uploading and

06:34

downloading content

06:36

now again for demonstration purposes the

06:39

website is actually hosted on a

06:41

third-party Cloud I also have automated

06:44

traffic running to simulate visitors

06:46

accessing the site

06:48

so now I'm going to go over and head

06:49

over to my cloudflare dashboard and here

06:52

you can see I have cash Reserve enabled

06:55

and it shows the current amount of data

06:57

stored in cash Reserve as well as the

06:59

total aggregate storage used over the

07:02

specific time period and you also have a

07:04

view of total cash Reserve read and

07:06

write operations once enabled cash

07:09

Reserve will start caching files with a

07:11

retention period of 30 days which will

07:13

be reset on any hits

07:15

customers can also pause using cash

07:17

Reserve meaning cloudflare's network

07:19

will no longer use cash Reserve to serve

07:21

data

07:22

here under overview you can see the

07:25

overall cash status including content

07:27

served by cloudflare and content served

07:30

by the origin

07:31

you can see the vast majority of

07:33

requests are served by cloudflare and if

07:36

you scroll down here and hover over the

07:38

cast status you can see a

07:41

92.96 cash hit ratio really good now

07:45

since I just enabled cash reserve a few

07:47

days ago if I go up here instead of 24

07:50

hours I select previous 30 days

07:54

we could see the cash hit ratio was

07:56

lower at around 80 percent so cash

07:59

Reserve really helped get into that 90

08:01

plus ratio getting us closer and closer

08:04

to that hundred percent

08:06

and scrolling down here you can see more

08:08

overall caching details in general like

08:10

the most popular content types and what

08:13

specific content is the most popular

08:15

here on the left you can also Purge the

08:17

cache which will also Purge content and

08:19

cash reserves you can also create page

08:21

rules to get more granular on any

08:23

specific caching behavior let's go into

08:26

this and take a look in more detail you

08:28

can see I created a page rule matching

08:31

on all requests that contain this

08:33

specific domain name

08:34

and I set the cache level to Cache

08:37

everything that's cachable but also can

08:39

select different cash level including

08:41

bypassing cache if desired

08:43

so now I'm gonna head over to caching

08:45

and look at Cash rules

08:48

so under cash rules I can also create a

08:51

rule as I did here to override ttls from

08:54

Cache control headers

08:56

this is done right at the edge and you

08:58

can see here if I click into it

09:00

all requests to this hostname

09:03

I've configured as content eligible for

09:06

caching and overridden the origin TTL

09:08

setting it to 12 hours with cloudflare

09:11

httl it makes it very convenient to set

09:14

TTL in one place for all assets

09:17

now I'm going to head over to analytics

09:19

and logs there

09:21

and I'll go under logs you can see I've

09:24

set up a log push I'm just going to

09:25

click edit here

09:27

last thing I want to show here is you

09:29

can also log data to external logs and

09:31

include the cash Reserve used field to

09:34

get more visibility into requests and

09:36

respective content being served from

09:38

cash Reserve I hope you found this

09:40

cloudflare cash Reserve walkthrough in

09:42

demo informational and useful for

09:44

additional details make sure to check

09:45

out the cloudflare cash Reserve product

09:47

page