AWS MediaConvert ã䜿çšãããµãŒããŒã¬ã¹åç»åŠçãã€ãã©ã€ã³
ãã®åç»ãã©ãããã©ãŒã ã¯ãã¢ããããŒããå°ãªã鿣æãããæ°çŸã®ãžã§ããåæã«çºçããããŒã¯æãŸã§ãå€åãããšã³ã³ãŒãã¯ãŒã¯ããŒãã«å¯Ÿå¿ã§ãããã¹ã±ãŒã©ãã«ã§è²»çšå¯Ÿå¹æã®é«ãæ¹æ³ãå¿ èŠãšããŠããŸããã
ãããžã§ã¯ããçžè«ãã
課é¡
åºå®å®¹éã®ãšã³ã³ãŒãã€ã³ãã©ã¯ãéå°ããããžã§ãã³ã°ïŒé«ã³ã¹ãïŒããäžè¶³ããããžã§ãã³ã°ïŒäœéïŒã®ããããã§ãã:
- ãšã³ã³ãŒãã¯ãŒã¯ããŒããéåžžã«å€åãããããäºæž¬äžèœã ã£ã
- ã³ã³ãã³ãå ¬éæã«ã¯ãããŒã¯æã«éåžžéã®100åã®ãã©ãã£ãã¯ãçºçããããšããã£ã
- 鿣æã«å°çšã®ãšã³ã³ãŒããµãŒããŒã24æé365æ¥çšŒåãããã®ã¯è²»çšããããããã
- ãžã§ãã®å€±ææã«ã¯ãæåä»å ¥ãªãã«èªåæ€åºãšãªãã©ã€ãå¿ èŠã ã£ã
ç§ãã¡ã®ãœãªã¥ãŒã·ã§ã³
ç§ãã¡ã¯ãAWS Lambda ããªã¬ãŒãš AWS MediaConvert ã䜿çšãã䌞瞮èªåšã§åŸé課éå¶ã®åç»åŠçãè¡ããµãŒããŒã¬ã¹ãšã³ã³ãŒãã£ã³ã°ãã€ãã©ã€ã³ãå®è£ ããŸããã
ã¢ãŒããã¯ãã£
- ããªã¬ãŒ: S3 ã¢ããããŒãã€ãã³ããç£èŠãã AWS Lambda 颿°
- ãšã³ã³ãŒã: ããŒãããŒåºæã®ãžã§ããã³ãã¬ãŒãã䜿çšãã AWS MediaConvert
- ã¡ãã»ãŒãžã³ã°: éåæãžã§ãã¹ããŒã¿ã¹æŽæ°ã®ããã® ActiveMQ/STOMP
- ç£èŠ: ãžã§ãã®é²æç¶æ³ã远跡ãã NestJS ãšã³ã³ãŒããŒããã¯ãšã³ã
- ã¹ãã¬ãŒãž: å ¥åºåã¢ã»ããçšã® AWS S3
ãã€ãã©ã€ã³ãããŒ
- S3 ã€ãã³ã - åç»ã¢ããããŒãã Lambda 颿°ãããªã¬ãŒ
- ãžã§ãèšå® - Lambda ãããŒãããŒãããã¡ã€ã«ãèªã¿èŸŒã¿ãMediaConvert ãžã§ããæ§ç¯
- éä¿¡ - é©åãªåºåèšå®ã§ MediaConvert ãžã§ããéä¿¡
- é²æè¿œè·¡ - STOMP ã¡ãã»ãŒãžããšã³ã³ãŒããŒããã¯ãšã³ãã«ã¹ããŒã¿ã¹ãäžç¶
- å®äº - åºåã¢ã»ããã S3 ã«ä¿åãã¡ã¿ããŒã¿ã MongoDB ã§æŽæ°
- ãšã©ãŒåŠç - 倱æãããžã§ããææ°é¢æ°çããã¯ãªãã§ãªãã©ã€ãã¥ãŒã«è¿œå
äž»ãªæ©èœ
- ã¢ã€ãã«ã³ã¹ããŒã - Lambda ãš MediaConvert ã¯å®éã®äœ¿çšéã«å¯ŸããŠã®ã¿èª²é
- 匟åçãªã¹ã±ãŒãªã³ã° - 1ãã1000以äžã®åæãšã³ã³ãŒããžã§ããåŠç
- ããŒãããŒãã³ãã¬ãŒã - ããŒãããŒããšã«äºåèšå®ããã MediaConvert ãžã§ããã³ãã¬ãŒã
- ã€ãã³ãããªãã³ - S3 ã€ãã³ãããšã³ã³ãŒãã¯ãŒã¯ãããŒãèªåçã«ããªã¬ãŒ
- å æ¬çãªç£èŠ - ãžã§ãã¹ããŒã¿ã¹ãæéããšã©ãŒè¿œè·¡
ææ
æè¡ã¹ã¿ãã¯
caseStudyDetail.more ã±ãŒã¹ã¹ã¿ãã£
ãã®ä»ã®æè¡å®è£ äºäŸãã芧ãã ãã
SCTE-35ããŒã«ãŒè§£æãšãã«ããã©ãããã©ãŒã ãã¬ã€ã€ãŒçµ±åã«ããã¯ã©ã€ã¢ã³ããµã€ãåºåæ¿å ¥ (CSAI)
ãããããªã¹ããªãŒãã³ã°ãã©ãããã©ãŒã ã¯ããŠã§ããã¢ãã€ã«ãã³ãã¯ãããTVã¢ããªå šäœã§ã¯ã©ã€ã¢ã³ããµã€ãåºåæ¿å ¥ (CSAI) ãå®è£ ããå¿ èŠããããŸãããããã«ããããµãŒããŒãµã€ãæ¿å ¥ã§ã¯æäŸã§ããªããå®å šãªåºåã€ã³ã¿ã©ã¯ã·ã§ã³ãµããŒãïŒã¯ãªãã¯å¯èœãªãªãŒããŒã¬ã€ãã³ã³ãããªã³ãããŒãã¹ããããã¿ã³ïŒãåãããããŒãœãã©ã€ãºãããããã€ã¹ã¬ãã«ã®åºåäœéšãå¯èœã«ãªããŸãã
SCTE-35ã¢ãããŒã«ãŒã·ã°ããªã³ã°ïŒã¡ãã£ã¢ãã¬ãŒã©ãŒæ¿å ¥ãã€ãã©ã€ã³
ããã¹ããªãŒãã³ã°ã¡ãã£ã¢äŒæ¥ã¯ãSCTE-35ã¢ãããŒã«ãŒãã©ã€ãããã³VODã¹ããªãŒã ã«æ¿å ¥ããããã¢ãŒã·ã§ã³çšãã¬ãŒã©ãŒïŒãã¬ããŒã«ããããããŒã«ããã¹ãããŒã«ïŒãæ£ç¢ºãªã¿ã€ãã³ã°ã§æ¿å ¥ã§ããå ç¢ãªèªååãã€ãã©ã€ã³ãå¿ èŠãšããŠããŸãããããã«ãããFASTãã£ã³ãã«ãã©ã€ãã€ãã³ãããªã³ããã³ãã³ã³ãã³ãã©ã€ãã©ãªå šäœã§ã®åçåãå¯èœã«ãªããŸãã
ãããã質å
MicrocosmWorks designed a segmented processing architecture where Step Functions orchestrate the pipeline: Lambda functions split source videos into segments, AWS MediaConvert handles the actual transcoding without Lambda timeout constraints, and a final Lambda stitches the output. This hybrid approach keeps the serverless cost model while supporting videos of any duration.
MicrocosmWorks measured a 70-85% cost reduction for bursty video processing workloads compared to running dedicated EC2 encoding instances. The serverless pipeline incurs zero cost when idle and scales to hundreds of concurrent jobs during peak periods, with AWS MediaConvert's per-minute pricing eliminating the need to provision for peak capacity.
MicrocosmWorks configured AWS Step Functions with per-step retry policies and exponential backoff, ensuring that a failed transcode step retries automatically without restarting the entire pipeline. Each stage writes intermediate outputs to S3, so recovery resumes from the last successful checkpoint rather than reprocessing from the source file.
MicrocosmWorks optimized the pipeline for near-real-time use cases with cold start mitigation using provisioned concurrency on critical Lambda functions and MediaConvert reserved transcoding slots. For live workflows, the pipeline achieves 2-5 minute end-to-end latency from upload to delivery, which is suitable for clip extraction and highlights distribution.
MicrocosmWorks builds serverless video infrastructure at rates of $25-$45/hr, with a complete MediaConvert-based pipeline including Step Functions orchestration, S3 lifecycle management, and monitoring typically requiring 250-400 development hours. The architecture's pay-per-use model means clients only pay AWS costs proportional to their actual processing volume.
ããžãã¹ã®å€é©ã®æºåã¯ã§ããŠããŸããïŒ
ã客æ§ã®èª²é¡ã«é¡äŒŒã®ãœãªã¥ãŒã·ã§ã³ãé©çšããæ¹æ³ã«ã€ããŠè©±ãåããŸãããã