How to build a Netflixlike multiscreen OTT service.docx

上传人:b****4 文档编号:12053214 上传时间:2023-04-16 格式:DOCX 页数:28 大小:692.69KB
下载 相关 举报
How to build a Netflixlike multiscreen OTT service.docx_第1页
第1页 / 共28页
How to build a Netflixlike multiscreen OTT service.docx_第2页
第2页 / 共28页
How to build a Netflixlike multiscreen OTT service.docx_第3页
第3页 / 共28页
How to build a Netflixlike multiscreen OTT service.docx_第4页
第4页 / 共28页
How to build a Netflixlike multiscreen OTT service.docx_第5页
第5页 / 共28页
点击查看更多>>
下载资源
资源描述

How to build a Netflixlike multiscreen OTT service.docx

《How to build a Netflixlike multiscreen OTT service.docx》由会员分享,可在线阅读,更多相关《How to build a Netflixlike multiscreen OTT service.docx(28页珍藏版)》请在冰豆网上搜索。

How to build a Netflixlike multiscreen OTT service.docx

HowtobuildaNetflixlikemultiscreenOTTservice

WiththefallofMegaupload,legalVODsitesarequicklygainingbackpopularityasconsumersareeagertowatchfreshvideocontentsonalltheirconnecteddevices.Ifyouareacontentowner,aTVchanneloratelco,itmaybetherighttimeto(re)launchyouMultiscreenOTTVODoffer.Thispostintendstostartfromthereferencetechchoicesinthisgame–Netflix’sones–explainthemajorchallengesofsuchtypeofserviceandtheassociatedDRMissues,andfinallydriveyouthroughoutthedifferentmarketoptionsyouhavetosetupyourownserviceonaclosebasis (thispartiscoveredin part2ofthepost).EverythingwouldhavebeeneasierifNetflixdidsellitssolutionasawhitelabelplatform,butit’snot(yet)thecase,sothisleavesfunterritoriestoexplore!

Asabackgroundinformation,thispostisbasedontheauthor’sexperienceofdeployingaMultiscreenOTTserviceforamajorFrenchbroadcasterwhilerelyingonSyncTVassolutionprovider,aswellasotherstudiesfortelcousecases.

LearningfromNetflix

Tomakealongsuccessstoryshort,Netflix’sonereliesonseveralkeytechnologicalchoices:

NetflixAPIDeviceEndpointprinciple

- APIreign :

theirAPI,launchedin2008,isthefoundationofalltheirplatform,thealpha&theomegaofservicereusabilityandagiledevelopmentonamaximumofheterogenousclientplatforms.TheygotcleverAPIarchitecturewithdedicatedendpointsbydevices(readlatest APIarchitectureredesign storyhere)tooptimizethedataexchanges,APIdegradabilitystrategies[Watchpresentation byDanielJacobson,DirectorofEngineering,API]…ThisisdefinitelythemajorkeyofNetflixsuccessandthereasonwhytheirAPIgeneratesthemosttrafficintheUSforasingleservice.APIdevelopmentshalldefinitelybeonyourtopprioritylist…

- Widecross-platformclientsupport :

Netflixisnowavailableonhundredsofdifferentclientplatforms(PCs,smartphonesandtablets,gameconsoles,connectedTVsandBluRayplayers,connectedmediaplayers…)allowingtostartandfinishplaybackeverywheretheconsumerwishes.Ifyoudon’tprovidemultiscreensupport,yourserviceisboundtofail,soyoumustinvestheavilyonthistopicandhireacrewofbleeding-edgefrontenddevninjas.

NetflixPS3UI

- HTML5mutualization :

whilenot(yet)alloftheirclientapplication relyonHTML5 asatheUImedium,NetflixmadeasubstantialinvestmentonthistechnologyasitconveysadefinitiveadvantageasregardsdevelopmentsmutualizationandflexibilityofUIrepackaging.Theyprovedthatoncontrolledenvironments,theHTML5userexperiencehasnothingtoenvytonativeapps.GiventhefactthatconsumersareincreasinglyfacingHTML5frontends,theirtolerancetoless-shinyUIexperiencestendstoraise,andthat’sagoodpointforyou.Itgetscomplicatedcurrentlyifyoucan’tdeployyourownengineandhavetorelyonvariousHTML5/video/DRMcombosbutstillit’sagoodtargetforkeepingthedevbudgetslow.

- CustomWebkitengine :

 toachievethecross-platformreusabilityoftheircustomdevelopmentsandoptimizations,theywentforbuildingtheirownflavorofWebkit+QTengineanduseitasbasisfortheSDKtheyproposedevicemanufacturerstointegrate.Thismaybetheimpossibletargettoreachforyou,asthisrequiresaleveragingpowerthatfewbrandsapartfromNetflixdohaveonthemarkettoday.

- Streamingsecretsauce :

Netflixreliesona customDASHsubset + PlayReadyDRM (withaconfirmedpinchofWidevineDRMfortheWii)bundlethattheyembedintheirSDKanduseon(almostof)theirclientdeployments.Itallowsthemtoproducethestrictminimumofpackagedstreamsvariantsandthereforetominlimizetheirstorageneeds.WhilethiscombomightnotbeavailableasastandardonyourvarioustargetplatformsSDKs,it’sagoodobjectiveforyourprojectonthelongrun.AdditionalDRMsmightberequiredtocoverthewholeclientsrange,though.

- Cloudhosting&transcoding :

by migratingtheirplatformtothecloud duringthepastyear,Netflixhasachievedanincrediblejumptowardsscalabilityandfailover.WhilethismightbeoverkillforamediumsizeOTTproject,itgivesagoodclueofhowyoucanachievedimensioningforbothcontentpreparation/serviceandmassiveAPIservice.Thisisalsooneofthemostrocketsciencetopicsinthepanorama,soyou’llneedsharpbackend/workflowtalentstoachieveasimilardeployment…

OTTservicecomponentsanddecisioncriterias

TobuildyourNetflix-likeserviceyouwillneedtodeveloporintegrateawiderangeofservicecomponents(seefollowingdiagramforrequiredblocks).Hereisaninsightslistonkeypointstoevaluatewhenchoosingorbuildingasolution.

MultiscreenOTTServiceReferenceArchitecture

Generalpoints

∙Timetomarket :

thiswillbethekeydifferencebetweentechnologyoptions.BuildingeverythingfromscratchresultsobviouslyinthelongestTTMandhighestchallenge.Withthemostpackagedmarketsolutions,6monthsistypicallytheminimumdelaytogetdeployedonthefirstdevices–andthedelaygetshigherifthestartingpointforclientappsisonlytheserviceAPIandnotfull-fledgereferenceapps.

∙DRMcoverage :

choosingtherighttechnicalpartnersorrecruitingexpertsinthisdomainisakeysuccesspointasDRMsaremandatoryandthereisagoodchancethatseveralofthemwillbeusedtocoverallthetargetdevices.ThisimpliesmakingsurefromthebeginningthataddingnewDRMsontheplatformwillnothighlyimpactbackendarchitecture–that’stheroleofDRMumbrellaservers(NetflixlicensedIrdetoActiveCloak)whoprovideaunifiedbackendinterfacetoallDRMserversflavorsandmutualized businessrules:

seespecificDRMchapterbelow.

∙Deploymentmodel :

whetheryourAPIplatformwillbedeployedfullyinthecloud,onaSaaSmodeoron-premises/self-hosting,thiswillimpacttheplanningandchangethelevelofdifficulty.Whileclouddeploymentseemstobethemoststraightforward,it’salsoasourceofconcernoverredundancy.Not-in-thecloudSaaSbringsconcernsaboutSLA/scalabilityandself-hostingrequirestimetoreachtherequiredfailoveranddimensioninglevels.

∙Automation :

itmaysoundtrivialbutnooneshouldunderestimatetheneedtoperformautomatedtasksinOTTplatforms,rangingfromsendingtargetedemailsuponveryspecificcustomersituationstotriggeringbackupplanwhenmediaingestsfailorincreasingplatformavailabilitydynamicallywhenloadgetshigher.

∙UltraVioletcompliance :

whileitmaynotyetbeatopictoday,thereisachancethatUltraVioletfinallymanagestobecomeanewstandardindigitalmediabusinessasBluRaydidforphysicalmedia,whichmeansthatyourplatformwillhavetointegratewithotherserviceprovidersusingthisinteroperabilitymethod.Beingcompliantsincethebeginningthusmeansbeingrightontimewhenthemarket confirmsitschoices.

∙Second-Screensupport :

thissubjectbeinga highlypopularfeaturenowadaysforlive(andsoonforon-demandcontents),yourchosensolutionmustallowlinkingofcomplexandvariousmetadatatotheprograms(theactualdatasbeinghostedsomewhereelse)aswellastheirsynchronizeddisplayonsmartphonesandtablets.Thismeansintegrationwiththeright watermarkingorfingerprintingtechnologies onthebackendandsupportforthesynchronizationinsidethefrontends.

Contentpreparation(transcoding/DRM)

∙Deploymentmodel :

fortranscodingandDRMization,youcanmeetseveraltypesofdeploymentmodels.The on-premisesmodel istheold-fashionedonewhereyoutranscodeandDRMizecontentswithyourownprocessingfarm:

goodthingaboutthisoneisthatyouknowhowitperformsandthatyoucanadjustworkflowsmoreeasily.Thebadthingresidesinthefactthatit’snotquicktoscaleandthatitcanrequiretrickyengineeringtointegrateallneededDRMsorproduceexoticstreamformat+DRMcombinations,dependingonwhichtranscodingfarmyouareusing.The SaaSmodel isinterestingbecauseitoffloadstheengineeringchargeandthescalabilityissueontheserviceprovideryouchoose,butthisprobablywon’tbeadedicatedplatformwithinstantscalability,soyourcontentswillbeprocessedalongsideorafterotherclients’ones,meaninglonghoursofwaituntilthepackagedcontentsgetsavailableinthecatalogue.Finally,the Cloudmodel allowstobenefitfromscalabilityandrecentevolutionstowardsGPUaccelerationofEC2instances,butfewprovidersarealreadyofferingtherightcombinationofspeed,securityandDRMizationflexibilityyou’llneed.ItmightbemoresuitedtousetheCloudtooffloadjobswhenon-premisescapacityhasbeenreached.

∙Assetsmutualization :

herethegameistominimizethenumberofassetsthatyouwillhavetoproduceinordertodelivertoallyourtargetdevices.That’snotaneasytaskforthemomentasPCandmobiles/tabletsareabitaheadofconnectedTVsasregardsABRstreamingsupportandDRMsupportbutsituationisevolvingquicklyand,giventhefactthatPlayReadyforHLShasnotbeennormalizedasexpectedbyMicrosoft(instead,theydidputalltheireffortsbehindDASHsupport),theHLS+PlayReadycombinationcanjustbeconsideredasaquick-winbeforeageneralmigration toaDASH-basedcombination in2013.Asofnow,thepanoramaisabitpuzzled,andyouhavetoprovidemonoblockandfragmentedformatswithdifferentDRMsinordertosupportthecurrentdevicesgenerationsandbrands.Sotheplatformyouchoosemustsupportcurrentchaoticrequirementsandallowsmooth&quickmigrationtomorefederatingstandardslikeDASHcombinedwithPlayReadyorMarlin.

∙ABRsupport :

 HLS/SMOOTH/HDS/DASH.That’swhatyouneedtosupporttodelivertocurrentandupcomingdeviceswhi

展开阅读全文
相关资源
猜你喜欢
相关搜索

当前位置:首页 > 小学教育 > 其它课程

copyright@ 2008-2022 冰豆网网站版权所有

经营许可证编号:鄂ICP备2022015515号-1