serverless-offline VS aws-lambda-dotnet

Using local emulators like sam local, serverless-offline, localstack, etc.

Hi, I'm the creator of serverless-offline (https://github.com/dherault/serverless-offline), a NPM package for local serveless development on AWS.

I'm building a cool product and intend to launch Q1 2023. To gain traction from my target customers, I plan to place a discrete ad at the launch of every serverless-offline instance.

Does it seem like an ok move to you? Or is it something that repels you?

Best,

As the creator of serverless-offline, I am well placed to tell you that this is the time-effective solution. Plus, it costs way less than other solutions at smaller scales. But, again, going Kubernetes or otherwise will be a problem for the future.

https://github.com/dherault/serverless-offline https://github.com/lambci/docker-lambda

What if I didn’t need to push code to AWS every time I wanted to test something? All heroes don’t wear capes. Like a knight in shining armor, Serverless Offline comes barging in to save the day! At least now I can test all my code locally before pushing it to AWS. That’s a relief.

With classic Express servers, you can use a simple node script to get the server up and running to test locally. Serverless wants to be run in the AWS ecosystem making it. Lucky for us, David Hérault has built and continues to maintain serverless-offline allowing us to emulate our functions locally before we deploy.

With the serverless offline plugin you can speed up local dev is by emulating AWS lambda and API Gateway locally when developing your Serverless project.

Those mocks are by definition not real services so there are some behavior differences between the local environment and the cloud provider. For example, AWS API Gateway emulated by serverless-offline doesn't handle VTL locally the same as AWS does.

serverless-offline (https://github.com/dherault/serverless-offline) is a great tool to use for local development of serverless applications.

It's not a complete mirror image of what you get but it's close enough in my experience.

I saw this issue: https://github.com/aws/aws-lambda-dotnet/issues/245

Creating Lambda Project using Amazon.Lambda.Templates. I use Amazon.Lambda.Annotations because it will be similar to my previous console program, and we can use dependency injection.

Hopefully, this post will have intrigued you enough to check out the new framework, and try converting some of your existing functions into what I think is a much more readable and easier to comprehend format. Also, the development team is always interested in feedback, which you can supply in the issues folder of their repo. You can also find the design document for the annotations in this issue.

I don't think it's exactly what you're looking for, but you could try out the LambdaTestTool https://github.com/aws/aws-lambda-dotnet/tree/master/Tools/LambdaTestTool

According to this GitHub issue we need to add and configure an additional package when running a custom runtime on ARM:

I'm assuming API's are REST APIs. Those sound like excellent use cases for running as Lambda functions. If the API's are an ASP .NET Core Web API project it is possible to deploy that to Lambda using the Amazon.Lambda.AspNetCoreServer, https://github.com/aws/aws-lambda-dotnet/tree/master/Libraries/src/Amazon.Lambda.AspNetCoreServer, NuGet package. That can be a quick way to get something working and then later choose to rearchitect to a smaller more micro services architecture if necessary.

AWS provides a NuGet package (see Amazon.Lambda.AspNetCoreServer) that makes it easy to do this. It works pretty well, but instead of one copy of the API serving many clients you have many copies of the API each serving one client at a time. There are also limitations in areas like file upload and download (which vary depending upon whether this is being used with API Gateway or an Application Load Balancer).