Re:How Imgix Built a Stack to Serve 100k Images per Second
by jawngee on Monday August 31, 2015 @06:43AM
(#10146205)
Imgix is the middle, they process the parameters once and cache the result.
[ Parent
| on HN ]
Re:How Imgix Built a Stack to Serve 100k Images per Second
by ddorian43 on Monday August 31, 2015 @06:52AM
(#10146224)
That is just caching.
Middle is: You precompute some fixed presets(like him, lower latency) but also have the ability to generate on demand if a preset doesn't exist(used when adding new presets, no reason to wait *days to have the new preset).
Re:How Imgix Built a Stack to Serve 100k Images per Second
by skuhn on Monday August 31, 2015 @03:10PM
(#10148485)
Once you've built a system that works fast enough to handle image rendering work on-demand, then adding batch or precomputational features is largely just creating requester logic to ask for the image before the real demand arrives.