Amazon Elastic Transcoder vs. AWS CloudFormation

It is well suited in a large setting where people use different file formats and various apps to record and transfer their audio or video files across devices. In such scenarios, the transcoder would of real help to eliminate the hassle of converting the files into desired formats for viewing or doing some other analysis.

The transcoder would not be of much use if all the files have the same format and does not need any conversion from their source file formats. It would prove costly and not useful if it's just an additional step that is of no particular use

Incentivized

AWS CloudFormation is well suited for scenarios where all of your resources need to be provisioned on AWS but it is not suited for hybrid cloud deployments. It's very easy for someone new to learn. The level of customization offered as part of the template specifically for AWS services is great. There is also a UI tool where we can drag and drop the services we want and it generates an yaml file which is very easy to use. The visibility of stacks and its resources and one place where we can track and identify the issues in deployment is great.

Incentivized

• Works at scale, you can can transcode a high number of videos at the same time.
• Supports a good number of formats.
• Good integration with AWS S3 and other AWS Services.

Incentivized

• SaaS
• Paas
• Iaas
• On promises

Incentivized

• Amazon Elastic Transcoder requires a fair amount of setup.

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

Support for Amazon Elastic Transcoder is the same as any other service within AWS. If you are familiar with AWS, it is easy to start using Elastic Transcoder

Incentivized

Amazon Elastic Transcoder is in a league of its own when compared to other alternatives in the market. The most noticeable competitor would be either Microsoft or Adobe or Google. When I had a chance to compare Azure products and Amazon products, the difference is obvious and the experience provided by both the products are very different in terms of user experience and interaction with the application. The cost and availability also were taken into consideration when choosing between the two shortlisted choices. So we went with Amazon's product as it is widely used and has support and maintenance which is basically better than the competition.

Incentivized

We didn't look into anything else as Cloudformation was "built-in" for AWS, it just kind of made sense to go with that. Terraform was something that we briefly looked into Terraform but decides to stick with Cloudformation because our task was relatively "simple". Apparently if it's a bit more complex, Terraform might be the way to go.

Incentivized

• Less time for integration with this service if you are already in AWS stack
• No real time transcoding is a negative

Incentivized

• It has a positive ROI
• Less time inverted in bugs
• More stable source code

Incentivized