You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: system_design/content_delivery_network.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,6 @@ Roughly the opposite of pull based CDNs, instead of waiting for a user to ask fo
25
25
Obviously, this may result in extra processing that may or may not be needed if the new content is never asked, especially in locations with little to no traffic or a location that likes one sub section of a website more than other sections. Another con is that the content needs to be packaged up by the main server per update, increasing its load.
26
26
27
27
## When to use CDNs?
28
-
A great scenario to use CDNs is if most of the website content is static, say images, videos, documents that do not require input from your main server.
28
+
A great scenario to use CDNs is if most of the website content is static, say images, videos, documents that do not require input from your main server. Things like templates, user agreement, privacy, FAQs, contact us, logos and icons.
29
29
You can think of this as having the client side of the content independent to the server side content.
30
30
CDNs could also be used to host the static files while a different architecture or set of services handles the dynamic webpages if they were requested.
0 commit comments