title: Express.js app serverless, using Lambda or Functions - a good idea?
body: <p>Disclaimer: I admit this is more of a broad-ish best practice question, rather then a specific programming issue, however, I believe the SO bunch is the best audience for it. I am aware of this similar question (<a href="https://stackoverflow.com/questions/64457577/should-i-be-using-express-js-in-a-serverless-app">Should I be using Express.js in a Serverless app?</a>), but the answers don't seem to answer mine.</p>
  <p>I want to move an Express.js from AWS Lightsail/EC2 to serverless for typical reasons, and Lambda is my weapon of choice. However, a whole framework together with an app on top of it may be a bit hefty to be still considered a <em>function</em> and so possibly unsuitable to be run as such on AWS Lambda, or Google/Azure Functions. While I'm convinced <a href="https://bitbucket.org/blog/deploy-an-express-js-app-to-aws-lambda-using-the-serverless-framework" rel="noreferrer">it is doable</a>, is it a good idea? Wouldn't this setup kill efficiency and complicate handling things such as sessions states, ultimately defeat the purpose of serverless functions?</p>