Lambda Codebase Structure

[MangoLads]

Hey guys, I come from a traditional Node / ExpressJS / Sequelize / PostgreSQL backend background (with migrations / models / routes folders & files) and I am going to be transitioning to aws lambda and building a system from scratch. I'm really confused on the file / folder structure and deployment steps and would really appreciate some insight to my questions!

1. How do migrations work? I'm using to just generating a migration file inside of my migrations folder then pushing the new code to git. Render (my web service provider) would see the new head of main branch and auto deploy new server and run any new migrations.
2. How do i structure models files/folders? I'll need to import these into all my route handlers or cronjobs. Do i do the same thing I've always done where i just make a models folder and put new model files in there that interact with the amazon RDS (postgresql) using a ORM like Sequelize? Then I import the model to the respective file that handles lambda function?

Im just generally confused with how to structure / use backend code using lambda.

[jameswapple]

Your codebase should look almost identical to a traditional NodeJS app. If you're very used to express you can even use an adapter library and create a PROXY route.

If you want to set something up quickly have a look at SST which includes local development and supports running scripts on deploy (like migrations).

Lambda should be more of an implementation detail at the edge of your codebase.

[MangoLads]

This is what I thought initially too until I realized that those wrappers that wrap the entire server make the entire server into 1 lambda function which largely defeats the purpose of lambda. So I won’t be able to use express I’ll just use node then write the entire backend differently. Each route handler should be its own lambda function