> Express is an established node.js web framework and there is a wealth of third party middleware packages that may not be available in other form. The ExpressService base class uses aws-serverless-express to host an Express application. This is not intended to host existing Express applications but more as a solution to bridge the gap for specific functionalities, for example use Passport.js to implement user authentication.

Interesting, that's not something I've considered when building lambda functions in JS. Does this add to the cold start time? Probably, right?

I feel like, when using Lambda, the point is to be lean and not invoke a framework. Using the middleware makes sense, but why not add an adapter for the package you want to use?

I'm just spit-balling.