aws-lambda-runtime-interface-emulator VS fl-aws

Compare aws-lambda-runtime-interface-emulator vs fl-aws and see what are their differences.

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
aws-lambda-runtime-interface-emulator fl-aws
4 1
862 15
1.7% -
5.2 0.0
8 days ago about 7 years ago
Go
Apache License 2.0 Apache 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-lambda-runtime-interface-emulator

Posts with mentions or reviews of aws-lambda-runtime-interface-emulator. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-06-19.
  • Understanding the AWS Lambda Runtime API
    4 projects | dev.to | 19 Jun 2021
    Enter the aws-lambda-runtime-interface-emulator. This tool will allow us to emulate the AWS Lambda Runtime API locally (I suspect that the AWS SAM uses this tool under the hood as well). The aws-lambda-runtime-interface-emulator is designed to be used with Docker. Still, nothing stops us from containerizing our code for the sake of development and then, whenever we are ready, proceeding with deployment how we wish to. This local workflow is a bit more involved than the previous one, but it might be a valid alternative for those not using AWS SAM or are already using containers to deploy their Lambdas.
  • Puppeteer performance in AWS Lambda Docker containers
    4 projects | dev.to | 5 May 2021
    There is a special tool to test AWS Lambda images locally. It's called AWS Lambda Runtime Interface Emulator (RIE). You have two options: include RIE in your image or install it locally. We don't need it in the production image, so let's choose the second option. We will download binary locally and mount it to our image if we need to test it.
  • Ask HN: Does anyone else find the AWS Lambda developer experience poor?
    23 projects | news.ycombinator.com | 18 Apr 2021
    Suggestions:

    1. If you are building APIs and using Lambda functions as targets from an API Gateway API, look into libraries like serverless-wsgi (Python) or wai-handler-hal (Haskell) that translate between API Gateway request/response payloads and some kind of ecosystem-native representation. Then as long as you're writing code where all state gets persisted outside of the request/response cycle, you can develop locally as if you were writing for a more normal deploy environment.

    2. Look into the lambda runtime interface emulator ( https://github.com/aws/aws-lambda-runtime-interface-emulator... ). This lets you send invoke requests to a fake listener and locally test the lambda more easily. While the emulator is provided in the AWS container base images, you don't need to run it inside a container if you're deploying with zip files. (AWS-provided container images automatically enable the emulator if not running in a lambda runtime environment, and using docker for port remapping is nice. But not at all required.)

    3. Get really good at capturing all requests to external services, and mocking them out for local testing. Whether this is with free monads, effect systems, gateway classes will depend on your language and library choices.

    23 projects | news.ycombinator.com | 18 Apr 2021

fl-aws

Posts with mentions or reviews of fl-aws. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-04-18.
  • Ask HN: Does anyone else find the AWS Lambda developer experience poor?
    23 projects | news.ycombinator.com | 18 Apr 2021
    Living in my team's bubble i thought everyone runs or tries to run parallel environments: prod, staging, dev, but also an individual (person) or feature env. Why? Because there's no emulator or documentation that will teach you real behavior. Like others have said, AWS seems out of this world. Just like GCP and Azure i might add. Some things you don't expect and they mesmerize you how smart they are. Some you expect and you can't fathom how come you're the "only" one screaming. Random thought: this is how i ended up logging all I bumped into into "Fl-aws" https://github.com/andreineculau/fl-aws

    Back to the point: reality is that many build their AWS environment (prod) manually, maybe they duplicate once (dev) also manually, maybe they use some automation for their "code" (lambda) but that's it. This implies it's practically impossible to run end-to-end tests. You can't do that in prod for obvious reasons and you can't do it in dev either - you have many devs queueing, maybe dev is not in sync with prod etc.

    My team ran cloudformation end-to-end. We actually orchestrated and wrapped cloudformation (this is yet another topic for not using terraform etc) so that if smth couldn't be done in CFN, it would still be automated and reproducible. Long story short, in 30 minutes (it was this long because we had to wait for cloudfront etc) we had a new environment, ready to play with. A total sandbox. Every dev had their own and it was easy to deploy from a release artifact or a git branch to this environment. Similarly you could create a separate env for more elaborate changes to the architecture. And test in a live environment.

    Finally to your question: how do you test end-to-end?

    If we talk about lambdas because that's where the business logic lies in a "serverless" architecture, then the answer is by calling the system which will eventually call your lambda/s along the way. If your lambda ia sitting behind AWS gateway, then fire an http request. Is it triggered when objects land on S3? Then push some object to S3. How do you assert? Just the same - http response, S3 changes etc. Not to mention you can also check cloudwatch for specific log entries (though they are not instant).

    With this type of a setup, which sounds complex, but it is not since it is 100% reproducible (also from project to project - I had several), adding this proxy-to-my-dev-machine lambda would mean I can make local changes and then fire unit AND end-to-end tests without any changes pushed to AWS, which is the main time/energy consumer imo.

    PS: sorry for the wall of text. Like i said i recently realized that the development realities have huge discrepancies, so i tried to summarize my reality :)

What are some alternatives?

When comparing aws-lambda-runtime-interface-emulator and fl-aws you can also consider the following projects:

Moto - A library that allows you to easily mock out tests based on AWS infrastructure.

serverless-application-model - The AWS Serverless Application Model (AWS SAM) transform is a AWS CloudFormation macro that transforms SAM templates into CloudFormation templates.

serverless-offline - Emulate AWS λ and API Gateway locally when developing your Serverless project

aws-lambda-go - Libraries, samples and tools to help Go developers develop AWS Lambda functions.

docker-lambda - Docker images and test runners that replicate the live AWS Lambda environment

chrome-aws-lambda - Chromium Binary for AWS Lambda and Google Cloud Functions

aws-lambda-python-runtime-interface-client

up - Deploy infinitely scalable serverless apps, apis, and sites in seconds to AWS.

faasd - A lightweight & portable faas engine

bref - Serverless PHP on AWS Lambda

gateway - Drop-in replacement for Go net/http when running in AWS Lambda & API Gateway

serverless-patterns - Serverless patterns. Learn more at the website: https://serverlessland.com/patterns.