Strong disagree here, there's little advantage to make separate lambda functions for each route in your server app. Microoptimizing cold start from an extra route is usually not an issue in these usecases. Keeping everything in an http library as you would without lambda is the simplest, as your routing logic is together and it's easy if u move off lambda.