aws-lambda alternatives and similar packages
Based on the "AWS" category.
Alternatively, view aws-lambda alternatives based on common mentions on social networks and blogs.
-
serverless-haskell
Deploying Haskell applications to AWS Lambda with Serverless -
stratosphere
Haskell EDSL and type-checker for AWS CloudFormation templates -
-
-
-
amazonka-s3-streaming
Provides a conduit based interface to uploading data to S3 using the Multipart API -
-
aws-kinesis-client
A producer/consumer client library for Kinesis -
-
-
-
-
-
aws-performance-tests
Performance Tests for the Haskell Bindings for Amazon Web Services (AWS) -
aws-sign4
Haskell implementation of the AWS Signature V4 protocol for signing HTTP requests -
aws-configuration-tools
Configuration types, parsers and renderers for AWS services using configuration-tools -
aws-cloudfront-signer
Haksell library package for signing URL requests to the AWS CloudFront service -
-
aws-elastic-transcoder
extension to the Haskell AWS repository to interface to the AWS Elastic Transcoder service -
-
aws-dynamodb-conduit
Conduit-based interface for AWS DynamoDB -
amazon-emailer
A simple daemon to process messages put into a postgresql table and mail them out using amazons SES.
WorkOS - The modern identity platform for B2B SaaS
Do you think we are missing an alternative of aws-lambda or a related project?
|
InfluxDB - Power Real-Time Data Analytics at Scale
sponsored
www.influxdata.com
|
Popular Comparisons
-
aws-lambdavsaws
-
aws-lambdavsamazonka
-
aws-lambdavsmessente
-
aws-lambdavsthemoviedb
-
aws-lambdavshs-GeoIP
|
SaaSHub - Software Alternatives and Reviews
sponsored
www.saashub.com
|
README
AWS Lambda: Haskell Bindings
This initially started off as another sister-project to aws, aws-kinesis
and aws-dynamodb-streams, built in the same general pattern. However, once I
had implemented the core along the lines of those libraries, I realized that
there was a massive amount of difficult-to-maintain boilerplate that did not
seem to be gaining me anything.
On the other hand, I realized that it would be very easy to reuse some the core
data types from aws-general, but then implement the rest of the machinery
locally using wreq, which provides built-in support for AWS V4 signing. I am
considering this project to be an experiment, then, in providing a slightly
more modern and less verbose core to the Haskell AWS bindings. I am confident
that anything which this library does not currently do (reusing connections,
etc.) can be added easily and modularly without significantly increasing the
complexity and burden of the project.
