offline-video-player VS serverless-express

Offline Video Player is a new Express MVC application allowing you to watch a lot of videos in a row, without distractions. It also keeps track of your progress automatically and let's you export/import it.

After building out a GPT powered endpoint, I wanted a low cost way of hosting it. At the time, I came across the serverless-express project https://github.com/vendia/serverless-express/tree/mainline, but no actual starter kits that would allow me to deploy it.

It’s all handled using https://github.com/vendia/serverless-express

Amplify gives an option of using a template and linking the API Endpoint with the Lambda and a connected DynamoDB table. I selected the template, Serverless Espress, which provided a lot of code in the template, though the majority of it felt overly bloated for what was effectively CRUD functionality.

With that in mind, the goal of this library is to be as lightweight as possible. There are other libraries out there that can handle express -> serverless mutation. See Serverless Express for that. If you want to rewrite as little code as possible, that is your best solution. With that being said, if the sole purpose of express is middleware and is only hosting a one-endpoint GraphQL server, I recommend rewriting to utilize this library.

To get Express to run on AWS Lambda the Node http stack needs to be emulated, or a full-blown HTTP/TCP server needs to be started and proxied to. Each of these workarounds require a ton of code from libraries like serverless-express.

Express is a framework/software. Lambda is compute. You can run express in Lambda. Ive done this and it was great. Check out https://github.com/vendia/serverless-express. The cool thing is that it's portable - you can build for one compute environment, and move it to another if it doesnt suit

Yea its fine use https://github.com/vendia/serverless-express since you are using express

Serverless Express - library that makes our "plain" NestJS API play nicely with Serverless

Some people like the Unix philosophy of "Do one thing and do it well" for Lambdas, others would build a monolithic app using a single Lambda with built in "routes". Both designs have pros and cons.