[GH-ISSUE #179] Question: What about the CDN service? #685

New issue

Closed

opened 2026-03-15 15:02:49 +03:00 by kerem · 2 comments

kerem commented

2026-03-15 15:02:49 +03:00

Owner

Originally created by @Xplouder on GitHub (Aug 9, 2018).
Original GitHub issue: https://github.com/flyimg/flyimg/issues/179

Using this service, even if we gain the flexibility to manipulate the images as we want, we lose the performance benefits that a CDN directly provide right? I mean, in the best scenario even if we store the cache in a CDN, this service will always be a proxy for it, right? Resulting in adding a layer to our request.
Thanks!

Originally created by @Xplouder on GitHub (Aug 9, 2018). Original GitHub issue: https://github.com/flyimg/flyimg/issues/179 Using this service, even if we gain the flexibility to manipulate the images as we want, we lose the performance benefits that a CDN directly provide right? I mean, in the best scenario even if we store the cache in a CDN, this service will always be a proxy for it, right? Resulting in adding a layer to our request. Thanks!

kerem closed this issue

2026-03-15 15:02:54 +03:00

kerem commented

2026-03-15 15:03:00 +03:00

Author

Owner

@baamenabar commented on GitHub (Aug 10, 2018):

Nope, actually I have https://i.m0.cl behind a CDN myself (cloudflare), but any CDN should work just as fine.

The "caching" flyimg does is for the transformation of the image, which is stored as a file and served through an nginx server regularly. That image we serve with the proper http headers so a CDN can cache it for a year (the default expiration time we have for images), although most CDNs have a lower TTL and will hit the origin server at least once a day (Like amazon Cloudfront).

In short Flyimg can be used as an origin server from where a CDN could get and cache images.

I hope this anserws your question, if not give me a bit more detail on your planned or current setup and I can come up with a deeper explanation.
Cheers!

@baamenabar commented on GitHub (Aug 10, 2018): Nope, actually I have https://i.m0.cl behind a CDN myself (cloudflare), but any CDN should work just as fine. The "caching" flyimg does is for the transformation of the image, which is stored as a file and served through an nginx server regularly. That image we serve with the proper http headers so a CDN can cache it for a year (the default expiration time we have for images), although most CDNs have a lower TTL and will hit the origin server at least once a day (Like amazon Cloudfront). In short Flyimg can be used as an *origin* server from where a CDN could get and cache images. I hope this anserws your question, if not give me a bit more detail on your planned or current setup and I can come up with a deeper explanation. Cheers!

kerem commented

2026-03-15 15:03:05 +03:00

Author

Owner

@Xplouder commented on GitHub (Aug 11, 2018):

I see, so you use a CDN on top of it, makes sense. Thank you for the quick response.

@Xplouder commented on GitHub (Aug 11, 2018): I see, so you use a CDN on top of it, makes sense. Thank you for the quick response.