3 ms·
It’s what I know best and what I’m most productive in. The project is to get something running and learn a handful of new things, and learning a new framework w
by zrail 8y ago
It’s what I know best and what I’m most productive in. The project is to get something running and learn a handful of new things, and learning a new framework would be a detriment to that first goal.
The manager app is not in the hot path with this design so performance doesn’t matter all that much.
- michaelgv 8y agoAre you designing this CDN to pull from origin, cache temporarily? Or to pull from local file and put strong cache on it? If you need a hand let me know, I’ve built pretty large CDNs before (10M r/s at peak)
- zrail 8y agoThe former to start but I want to add push zones and/or “s3sync” zones that proactively sync an s3 bucket to local disk. Thanks for the offer! I might just take you up on it :)
- michaelgv 8y agoJust be careful, understand that if you do a PULL only CDN, you're not going to gain big benefits. If you do want a pull only CDN, have a background task runner to retrieve the files, and update them locally.
- zrail 8y agoSure. I have Nginx set to keep files around for s long time and serve stale and refresh in the background, but proactively refreshing periodically is a good idea.
- tatersolid 8y ago> understand that if you do a PULL only CDN, you're not going to gain big benefits. This statement makes no sense. A CDN edge node is just a cache; its size and your access patterns determine the hit ratio. At $dayjob we get Nginx cache hit ratios on our edge in excess of 99% for “an origin fetch” setup. That is a very large benefit. Cloudflare works entirely on origin fetch. They seem to be doing okay.