AWS Media Services – Process, Store, and Monetize Cloud-Based Video

Re:AWS Media Services – Process, Store, and Monetize Cloud-B... by schwank on Monday November 27, 2017 @10:57AM (#15788271)

Elastic Transcoder could not handle 4K video, and only worked with static files stored in S3 - it wasn't designed for streaming content.

AWS purchased Elemental in 2015. There is some overlap but Elemental Media* services are more flexible and provide JIT encoding and dynamic ad insertion, to serve a broader market than ET did.

Disclaimer: AWS employee.

[ Parent | on HN ]

Re:AWS Media Services – Process, Store, and Monetize Cloud-B... by rloc on Monday November 27, 2017 @12:00PM (#15788811)

HLS, Smooth streaming, MPEG-Dash are all designed for streaming and that's what we use with Elastic Transcoder today. Used in conjunction with Amazon Cloudfront, I thought it was perfect for streaming content.

Does that mean we'll need to manually transition to the new services ? Are you planning a bridge or something ?

What about the cost of transcoding everything a second time ?

[ Parent | on HN ]

Re:AWS Media Services – Process, Store, and Monetize Cloud-B... by nikolay on Monday November 27, 2017 @11:59AM (#15788788)

Instead of fixing Elastic Transcoder, there's yet another and better way of doing the old thing. Much similar to what happened with SimpleDB, OpsWorks, etc.

[ Parent | on HN ]

Re:AWS Media Services – Process, Store, and Monetize Cloud-B... by erikpukinskis on Tuesday November 28, 2017 @03:46AM (#15795471)

The alternative is shutting down your 1.0 when you release your 2.0. Keeping the 1.0 service running in maintenance mode seems pretty helpful to me.

[ Parent | on HN ]

Re:AWS Media Services – Process, Store, and Monetize Cloud-B... by nikolay on Wednesday November 29, 2017 @03:32PM (#15810569)

No, the alternative is a design pattern called Façade, i.e. having the new backend support the old API via a translation layer either in the SDKs or in the infrastructure layer.

[ Parent | on HN ]