My idea for a smart fault tolerant assets / CDN balancer?
My idea is to store assets on multiple networks/CDN providers. Label them assets-n1, assets-n2, etc. The user is given an roughly equal amount of assets to load from each network during the evaluation session. Load times are taken by javascript which are then sent back to the load balancer. Going forward the user is sent to the fastest/cheapest network through simple HTML markup. This allows the ability to add edge CDN nodes where the CDN provider is not located or is providing bad performance. This allows the automated routing around temporary bad performance.
I am a little inexperienced and wonder if I could get input for improvements from the HN community. Maybe you know someone who has implement something like this? Maybe you want to implement yourself and share it with everyone?
-- savr
4 comments
[ 2.3 ms ] story [ 20.4 ms ] threadThis is my motive for such a solution. Plus I have the benefit of it being able to routing around problems with little manual effort.