hz3 VS amazonka

Compare hz3 vs amazonka and see what are their differences.


Haskell bindings to Microsoft's Z3 API (unofficial). (by IagoAbal)


A comprehensive Amazon Web Services SDK for Haskell. (by brendanhay)
Our great sponsors
  • Onboard AI - ChatGPT with full context of any GitHub repo.
  • WorkOS - The modern API for authentication & user identity.
  • InfluxDB - Power Real-Time Data Analytics at Scale
hz3 amazonka
0 7
57 588
- -
1.6 9.6
25 days ago about 2 months 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.


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

We haven't tracked posts mentioning hz3 yet.
Tracking mentions began in Dec 2020.


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 2023-12-09.
  • Getting Amazonka S3 to work with localstack
    2 projects | /r/haskell | 9 Dec 2023
    This is perhaps not as obvious as it could be. A penny for your thoughts? https://github.com/brendanhay/amazonka/issues/968
  • stack
    7 projects | /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 | /r/haskell | 28 Nov 2021
  • Haskell ghost knowledge; difficult to access, not written down
    13 projects | /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 hz3 and amazonka you can also consider the following projects:

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

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

aws - Amazon Web Services for Haskell

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

hs-GeoIP - Haskell bindings to the MaxMind GeoIPCity database

aws-lambda - Haskell bindings for AWS Lambda

loup - Simple Workpools

ec2-unikernel - Tool for uploading unikernels into EC2

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

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

minio-hs - Minio Client SDK for Haskell

aws-sdk - AWS SDK for Haskell