aws-elastic-transcoder VS amazonka

Compare aws-elastic-transcoder vs amazonka and see what are their differences.

aws-elastic-transcoder

extension to the Haskell AWS repository to interface to the AWS Elastic Transcoder service (by iconnect)

amazonka

A comprehensive Amazon Web Services SDK for Haskell. (by brendanhay)
Our great sponsors
  • Scout APM - Truly a developer’s best friend
  • Zigi - The context switching struggle is real
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • SonarQube - Static code analysis for 29 languages.
aws-elastic-transcoder amazonka
0 5
1 545
- -
0.0 9.9
almost 9 years ago 5 days ago
Haskell Haskell
BSD 3-clause "New" or "Revised" License Mozilla Public License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

aws-elastic-transcoder

Posts with mentions or reviews of aws-elastic-transcoder. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning aws-elastic-transcoder yet.
Tracking mentions began in Dec 2020.

amazonka

Posts with mentions or reviews of amazonka. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-17.
  • stack
    7 projects | reddit.com/r/haskell | 17 Jul 2022
    Stack does not clone a copy of a git package for each of a user's projects that uses the package but cabal does. This can be a deal-breaker for cabal when using huge git projects like https://github.com/brendanhay/amazonka that can take forever to git clone. If you have a test/CI setup for a project that uses such packages, cabal's lack of caching can also cause huge delays and more opportunities for failure (from network errors or timeouts). From the proceedings of past issues, I don't think cabal devs are interested in addressing this use case. https://github.com/haskell/cabal/issues/5586
  • Amazonka 2.0.0-rc1 is ready for testing
    2 projects | reddit.com/r/haskell | 28 Nov 2021
  • Haskell ghost knowledge; difficult to access, not written down
    13 projects | reddit.com/r/haskell | 24 Jan 2021
    amazonka is a bit of a minefield despite being listed as the only AWS library by SOTU

What are some alternatives?

When comparing aws-elastic-transcoder and amazonka you can also consider the following projects:

amazonka-s3-streaming - Provides a conduit based interface to uploading data to S3 using the Multipart API

amazon-emailer - A simple daemon to process messages put into a postgresql table and mail them out using amazons SES.

aws-ec2 - Now maintained by: See https://github.com/memcachier/aws-ec2

aws-lambda - Haskell bindings for AWS Lambda

aws-cloudfront-signer - Haksell library package for signing URL requests to the AWS CloudFront service

messente - Messente SMS Gateway for Haskell

minio-hs - Minio Client SDK for Haskell

aws - Amazon Web Services for Haskell

loup - Simple Workpools

serverless-haskell - Deploying Haskell applications to AWS Lambda with Serverless

aws-sdk - AWS SDK for Haskell

hs-GeoIP - Haskell bindings to the MaxMind GeoIPCity database