serverless-offline VS github-action

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.

Our deploys don't deploy on merges to main. For this though, we can just use the official Serverless Github Action. Alternatively, we could purchase a license to the Serverless Dashboard, but this option is a bit more expensive, and we're not using all of its features on this project. However, we've used this on other client projects, and it really helped us manage and monitor our deployments.

Now that we have our Serverless Deployment script ready, we can deploy this to AWS Lambda using this script with Github Actions.

Link da action no github https://github.com/serverless/github-action