#Lots of Images (CDN)?

16 messages · Page 1 of 1 (latest)

kindred wren
#

Since I'm writing a blog, my site will most likely have a lot of images eventually. Is it totally fine to throw them all into src or should I look into a CDN to serve them? If so, does anyone have any suggestions? I've never used one in projects before so any help is appreciated

bleak cobalt
#

Not much point in using one if you're just storing images on your host. You should really consider cloud storage instead.

mystic thicket
#

How many images are we talking here?

We've had people load at least a few thousand images from src... But really when you start to get into the multiple hundreds or thousands of images you want to be looking at probably using a cdn or CMS.

kindred wren
#

I'm using Decap if that matters. But what about serving from cloud storage? That's what I meant by a CDN since I thought that's what it did

kindred wren
mystic thicket
#

Hmmm never used Decap tbh, but if it's a headless CMS yeah I'd imagine you'd be using their CDN for images. At least for Storyblok that's how they do it. You'll render the content for each page in Storyblok, and it'll just go off and get the img src from the their cdn I'm pretty sure

kindred wren
#

Hmmmm that isn't how it's set up I don't think?

bleak cobalt
#

Decap used to be Netlify CMS so I'd imagine it tags onto a lot of Netlify services (like their media CDN), but probably only if you use their hosting.

bleak cobalt
# kindred wren I'm using Decap if that matters. But what about serving from cloud storage? That...

Cloud storage gives you an endpoint to serve your images from, whereas a CDN generally just caches those images short term. The point of a CDN is to reduce server load and latency, so instead of users hitting your server for every image and video file, their requests get routed through a regional cache that checks for your file and returns the cached media or forwards the request to your server.

Who's your hosting provider?

kindred wren
#

But uh it's deployed through Netlify

#

And DNS is through Netlify

#

Sooooo for all intents and purposes, it's Netlify lol

bleak cobalt
#

Yeah I don't know Netlify's current hosting packages but I'm pretty sure static deployments go straight to their CDN.

#

Hosting is different from domain registration btw. Sounds like you bought your domain from name cheap and imported it in netlify?

kindred wren
#

Yes