[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Disney+ CDN
- Subject: Disney+ CDN
- From: sneddon at gmail.com (sneddon at gmail.com)
- Date: Sat, 13 Apr 2019 00:58:51 -0700
- In-reply-to: <CAL9Qc[email protected]>
- References: <CAMRJ3AzQPS_iNSYoVXOaXZvEowGCy6MH9wTXGaMLnUEuruZY=w@mail.gmail.com> <[email protected]> <CAHuchRBwmnUBYCk=1fObSvM-Vhbgi8WAXPUqhdbWxBcKQcOmDA@mail.gmail.com> <CAL9Qc[email protected]>
Perhaps they are looking to build a hybrid solution? Thatâ??s what I would do.
According to open job positions at BAMTech, they are looking for engineers to drive â??on-premise, cloud, and third party distribution solutions. Working with the latest in streaming video, web serving and caching technologies.â?? There is also a CDN DevOps position open.
https://jobs.disneycareers.com/job/new-york/senior-software-engineer-cdn/391/10490558
-Dan Sneddon
> On Apr 12, 2019, at 12:34 PM, Tom Beecher <beecher at beecher.cc> wrote:
>
> I wouldn't expect them to build out anything until they got some usage data to determine the build/buy economics.
>
>> On Fri, Apr 12, 2019 at 3:02 PM Jared Geiger <jared at compuwizz.net> wrote:
>> An article mentioned BAMTech's platform which is what NHL, MLB, and HBO GO are built on. The bits from the first two come from Akamai and Level3 CDNs. I haven't looked into where HBO Go comes from.
>>
>>> On Thu, Apr 11, 2019 at 9:58 PM Aaron Gould <aaron1 at gvtc.com> wrote:
>>> Have we found out yet if Disney+ will have a CDN? Like Netflix oca, Akamai aanp, google ggc, facebook fna â?¦ a Disney isp-located cdn presence ?
>>>
>>>
>>>
>>> disneyplus.com
>>>
>>>
>>>
>>> -Aaron
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> From: NANOG [mailto:nanog-bounces at nanog.org] On Behalf Of Aaron Graves
>>> Sent: Saturday, December 29, 2018 7:22 PM
>>> To: nanog at nanog.org
>>> Subject: Disney+ CDN
>>>
>>>
>>>
>>> Anyone know what Disney is planning on doing for streaming content distribution once they leave Netflix? Would be nice if they'd provide an on-prem cache server.
>>>
>>>
>>>
>>> AG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190413/1e30432e/attachment.html>