3 ms·
Why would anyone want to use this over Dragonfly, which seems to have way more battle testing? Is this another case of NIH?
by marenkay 8y ago
Why would anyone want to use this over Dragonfly, which seems to have way more battle testing? Is this another case of NIH?
- ShakataGaNai 8y agoThis short answer seems to be "Timing". #1 - Dragonfly started November 2017 where as "Kraken was first deployed at Uber in early 2018". Which presumes Uber was working on this probably much earlier than Dragonfly even started. #2 - Dragonfly is still listed as a Sandbox CNCF project, where as Uber is running this in production for roughly a year it seems. #3 - Dragonfly was just refactored completely from Java to Go. So its kind of hard to say it's "battle tested" at all, at this point in time. It's basically an entirely new project as of 2 days ago.
- marenkay 8y agohttps://www.alibabacloud.com/blog/behind-alibabas-double-11-mysterious-dragonfly-technology-%C2%AEc-pb-grade-large-file-distribution-system_594074 https://www.alibabacloud.com/blog/behind-alibabas-double-11-... indicates Dargonfly existed much longer and was used in scenarios much larger than what Uber presented. What got into CNCF may be a newer iteration based on what Alibaba has been running but that means it should at least hold a candle to what is described in the post. With that said, one can surmise the Java version is the one they used in production. Apart from that, P2P image distribution is probably limited to internal uses that are not critical. Kind of missing indications of much difference in reliability to say an internal CDN this would give.
- monoian 8y agoKraken's readme included comparison with Dragonfly: https://github.com/uber/kraken#comparison-with-other-projects https://github.com/uber/kraken#comparison-with-other-project...