CDN — Sta je Content Delivery Network i zasto vam treba

Kompletni vodic: kako CDN ubrzava sajt, smanjuje latenciju i stiti od DDoS napada

50-70%
Smanjenje latencije sa CDN-om
300+
Cloudflare POP lokacija
$0
Cloudflare Free tier
100Tbps
Cloudflare mrezni kapacitet

Sadrzaj

  1. Sta je CDN i kako radi
  2. Zasto vam treba CDN
  3. Popularne CDN usluge
  4. Push vs Pull CDN
  5. CDN za staticke vs dinamicke sajtove
  6. Cloudflare besplatan setup
  7. Cache invalidation na CDN-u
  8. CDN i SEO
  9. Najcesce greske
  10. Reference i resursi

1. Sta je CDN i kako radi

CDN (Content Delivery Network) je mreza servera rasporedjena po celom svetu (edge servers / POP — Points of Presence). Umesto da svaki zahtev ide do vaseg origin servera (mozda u Americi), CDN servira sadrzaj sa najblizeg servera korisniku.

  • Korisnik iz Beograda → CDN edge server u Frankfurtu (~20ms) umesto origin u SAD (~150ms)
  • Korisnik iz Tokija → CDN edge u Tokiju (~5ms) umesto origin u SAD (~200ms)
  • Korisnik iz Njujorka → CDN edge u Njujorku (~3ms) umesto origin u istom gradu (~10ms)

Kako funkcionise (Pull CDN)

  1. Korisnik zatrazi vasajt.rs/style.css
  2. DNS resolvuje na CDN edge server (najblizi korisniku)
  3. Ako edge IMA kesiranu kopiju → odmah vraca (~20ms)
  4. Ako edge NEMA → zatrazi od origin servera, kesa i vraca korisniku
  5. Sledeci korisnik u istoj regiji dobija kesiranu verziju odmah
Analogija: CDN je kao lanac prodavnica umesto jedne centralne fabrike. Umesto da svi putuju do fabrike (origin server), kupuju u najblizoj prodavnici (edge server) koja se redovno snabdeva.

2. Zasto vam treba CDN

BenefitBez CDN-aSa CDN-om
Latencija100-300ms (zavisno od lokacije)5-30ms (najblizi edge)
DDoS zastitaOrigin server padaCDN apsorbuje napad (100+ Tbps)
SSLMorate konfigurisati samiAutomatski besplatan SSL
KompresijaMorate konfigurisatiAutomatski Brotli/Gzip
HTTP/3Kompleksna konfiguracijaAutomatski podrzan
SkaliranjeOrigin se ruzi pod pritiskomCDN distribuira opterecenje
UptimeOrigin down = sajt downCDN servira kesirani sadrzaj cak i kad origin padne

3. Popularne CDN usluge

CDNBesplatan tierPOP lokacijeDDoSNajbolje za
CloudflareDa (odlican!)300+Da (100+ Tbps)Sve — univerzalan izbor
Vercel EdgeDa (sa hostingom)~70OsnovnoNext.js / JAMstack sajtove
AWS CloudFront1TB/mesec free tier450+AWS ShieldEnterprise, AWS ekosistem
FastlyNe90+DaReal-time log, edge compute
Bunny.net14 dana trial120+DaNajjeftiniji ($0.01/GB)
Netlify EdgeDa (sa hostingom)~40OsnovnoStaticke sajtove, JAMstack
Preporuka 2026: Za vecinu sajtova, Cloudflare Free je najbolji izbor — besplatan CDN + SSL + DDoS + DNS + Brotli + HTTP/3. Za Next.js projekte, Vercel je prirodan izbor jer je CDN integrisan.

4. Push vs Pull CDN

TipKako radiPrimerPrednostiMane
Pull CDNCDN automatski vuche sa origin servera kad korisnik zatraziCloudflare, Vercel, BunnyJednostavno, automatskoPrva poseta moze biti spora (cache miss)
Push CDNVi rucno uploadujete fajlove na CDNAWS S3 + CloudFront, Bunny StoragePotpuna kontrolaZahteva CI/CD integraciju

Za vecinu sajtova Pull CDN je bolji izbor — nema potrebe za rucnim upload-om, CDN se sam brine o kesiranju.

5. CDN za staticke vs dinamicke sajtove

Staticki sajtovi (HTML/CSS/JS)

  • CDN kesa SVE — HTML, CSS, JS, slike
  • Origin server skoro nikad ne prima zahtev
  • Perfektan use case za CDN — 95%+ cache hit rate
  • Primer: blog, landing page, dokumentacija

Dinamicki sajtovi (API, baza)

  • CDN kesa staticke resurse (CSS, JS, slike) ali NE HTML/API odgovore
  • HTML se generise na origin serveru pri svakom zahtevu
  • I dalje velika korist: kompresija, SSL, DDoS zastita
  • Opcija: Edge Functions (Cloudflare Workers, Vercel Edge) — dinamicki sadrzaj na edge-u
stale-while-revalidate: Za dinamicki sadrzaj koji moze biti malo zastareo, koristite Cache-Control: s-maxage=60, stale-while-revalidate=86400 — CDN servira stari kes odmah i azurira u pozadini. Vise o cache strategijama u nasem HTTP Caching vodicu.

6. Cloudflare besplatan setup (korak po korak)

  1. Registrujte se na dash.cloudflare.com (besplatno)
  2. Kliknite "Add a Site" i unesite vas domen (npr. vasajt.rs)
  3. Izaberite "Free" plan
  4. Cloudflare skenira vase DNS zapise — proverite da su tacni
  5. Promenite nameservere kod vaseg registrara na Cloudflare-ove (npr. ns1.cloudflare.com)
  6. Sacekajte propagaciju (5 min do 24h, obicno ~30 min)
  7. Gotovo! Cloudflare sada rutira sav saobracaj kroz svoju mrezu

Posle setup-a, ukljucite

  • SSL/TLS: Encryption mode → "Full (strict)" za najjacu enkripciju
  • Always Use HTTPS: Edge Certificates → ON
  • Brotli: Speed → Optimization → Brotli: ON
  • Auto Minify: Speed → Optimization → HTML/CSS/JS: ON
  • HTTP/3: Network → HTTP/3: ON
  • Browser Cache TTL: Caching → postavite na 1 year za staticke resurse

7. Cache invalidation na CDN-u

Kad promenite sajt, CDN i dalje servira staru verziju dok kes ne istekne. Metode za forsiranje azuriranja:

  • Purge by URL: Cloudflare → Caching → Purge → Custom Purge → unesite URL-ove
  • Purge Everything: Cisti ceo CDN kes — koristite retko jer uzrokuje cache miss storm
  • API Purge: Automatizovano u CI/CD — curl -X POST "https://api.cloudflare.com/client/v4/zones/{id}/purge_cache" -d '{"purge_everything":true}'
  • Cache-busting: Hash u filename-u (style.a1b2c3.css) — novi fajl = novi URL = CDN automatski preuzima. Detaljnije u HTTP Caching vodicu.
  • Cache Tags: Enterprise feature — tagujete resurse i purge-ujete po tagu
Pravilo: Nikad ne kesirajte HTML na CDN-u za duzi period. Koristite s-maxage=0 ili no-cache za HTML, a dugotrajno kesiranje samo za staticke fajlove sa hash-om u imenu.

8. CDN i SEO

  • Brzina = bolji rang: Google koristi page speed kao faktor rangiranja. CDN smanjuje TTFB za 50-70% sto direktno poboljsava LCP (Core Web Vital).
  • Uptime = bolji crawling: Ako je sajt cesto nedostupan, Googlebot dolazi redje. CDN obezbeduje visoku dostupnost.
  • HTTPS besplatno: SSL je faktor rangiranja od 2014. CDN daje besplatan SSL.
  • Mobile speed: CDN dramaticno ubrzava mobilne korisnike (60%+ pretraga) jer smanjuje latenciju.
  • Canonical i redirect: Pazite da CDN pravilno prosleđuje canonical URL-ove i redirecte (www/non-www, HTTP/HTTPS).

9. Najcesce greske

  • Kesiranje HTML-a predugo — korisnici vide staru verziju sajta. HTML: no-cache ili s-maxage=0.
  • Zaboravljen Purge posle deploy-a — CDN servira stare CSS/JS. Koristite hash u filename-u.
  • Mixed content — HTTP resursi na HTTPS sajtu. CDN SSL ne resava ovo automatski — sve reference moraju biti HTTPS.
  • Origin IP exposed — Direktan pristup IP adresi origin servera zaobilazi CDN. Blokirajte pristup po IP-u.
  • Preskupljenje — Nepotrebni purge_everything → svi korisnici dobijaju cache miss odjednom → origin preopterecen.
  • CDN za lokalni sajt — Ako su svi korisnici u istom gradu kao server, CDN donosi minimalan benefiti (ali DDoS zastita vredi).
  • Websocket problemi — Neki CDN-ovi ne podrzavaju WebSocket bez konfiguracije. Cloudflare ga podrzava na Free planu.

10. Reference i resursi

Proverite brzinu vaseg sajta →

CDN — What is Content Delivery Network and Why You Need It

Complete guide: how CDN speeds up your site, reduces latency and protects from DDoS

50-70%
Latency reduction with CDN
300+
Cloudflare POP locations
$0
Cloudflare Free tier
100Tbps
Cloudflare network capacity

Table of Contents

  1. What is CDN and how it works
  2. Why you need CDN
  3. Popular CDN services
  4. Push vs Pull CDN
  5. Static vs dynamic sites
  6. Free Cloudflare setup
  7. Cache invalidation
  8. CDN and SEO
  9. Common mistakes
  10. References

1. What is CDN and how it works

CDN is a network of servers worldwide (edge servers / POP). Instead of every request going to your origin server, CDN serves content from the nearest server to the user.

Analogy: CDN is like a chain of stores instead of one central warehouse. Customers buy from the nearest store (edge) which regularly restocks from the warehouse (origin).

2. Why you need CDN

BenefitWithout CDNWith CDN
Latency100-300ms5-30ms
DDoS protectionOrigin crashesCDN absorbs (100+ Tbps)
SSLManual configFree automatic SSL
CompressionManual configAuto Brotli/Gzip
UptimeOrigin down = site downCDN serves cached even if origin is down

3. Popular CDN services

CDNFree tierPOPsBest for
CloudflareYes (great!)300+Universal choice
Vercel EdgeYes (with hosting)~70Next.js / JAMstack
AWS CloudFront1TB/mo free450+Enterprise, AWS
Bunny.net14-day trial120+Cheapest ($0.01/GB)
2026 recommendation: Cloudflare Free for most sites. Vercel for Next.js projects.

4. Push vs Pull CDN

Pull: CDN automatically fetches from origin on first request (Cloudflare, Vercel). Simple, automatic.

Push: You manually upload files to CDN (S3 + CloudFront). Full control, needs CI/CD.

Pull CDN is better for most sites.

5. Static vs dynamic sites

Static: CDN caches everything — 95%+ hit rate. Perfect use case.

Dynamic: CDN caches static assets (CSS, JS, images) but not HTML/API. Still valuable: compression, SSL, DDoS. Option: Edge Functions for dynamic content at edge.

6. Free Cloudflare setup (step by step)

  1. Sign up at dash.cloudflare.com (free)
  2. Click "Add a Site" and enter your domain
  3. Select "Free" plan
  4. Cloudflare scans DNS records — verify they're correct
  5. Change nameservers at your registrar to Cloudflare's
  6. Wait for propagation (~30 min)
  7. Enable: SSL Full (strict), Always HTTPS, Brotli, Auto Minify, HTTP/3

7. Cache invalidation on CDN

  • Purge by URL — clear specific URLs
  • Purge Everything — use rarely (causes cache miss storm)
  • API Purge — automate in CI/CD
  • Cache-busting — hash in filename (best approach). More in HTTP Caching guide.
Rule: Never cache HTML on CDN for long periods. Use s-maxage=0 for HTML, long-term caching only for static files with hash in name.

8. CDN and SEO

  • Speed = better ranking — CDN reduces TTFB by 50-70%, improving LCP
  • Uptime = better crawling — Googlebot crawls more when site is reliable
  • Free HTTPS — SSL is a ranking factor since 2014
  • Mobile speed — dramatically faster for 60%+ of searches

9. Common mistakes

  • Caching HTML too long — users see stale content
  • Forgotten purge after deploy — use hash in filenames
  • Mixed content — HTTP resources on HTTPS site
  • Origin IP exposed — direct IP access bypasses CDN
  • Excessive purge_everything — causes cache miss storm on origin

10. References and resources

Check your site's speed →
Performanse vodicPerformance Guide Core Web VitalsCore Web Vitals Optimizacija slikaImage Optimization HTTP CachingHTTP Caching Gzip i BrotliGzip & Brotli Lazy LoadingLazy Loading