You can create a project, put together multiple lambda config in a single project and it can have multiple different routes defined for each lambda. Container

You can create a project, put together multiple lambda config in a single project and it can have multiple different routes defined for each lambda. Container solutions scaled to zero, takes a lot more time to come online (cold start) compare to lambda environment. 1 serverless function serves one request, so when new functions are spinned to handle parallel requests, there can still be cold start for a lot of users. Not worrying about scale too early, We are looking to build a serverless tool and trying to understand if the market ready enough to finally move. Basically database compatibility with existing databases still seems like a big question : - Dynamodb's single table design has it's learning curve & hardly any availability of full text search, and much more complex stuff. - mongodb proxies are uncomman, and there is no pre build solution. ( even mongodb.com’s mongodb serverless and data api seems more like an incomplete products) - Rds proxy only available for database on aws. These are all concern, the existing app’s data in real world is sitting in databases on different cloud services be it mongodb, or sqls on GCP, Azure, DO or Aws. And without changing that database layer using serverless become really difficult and migration and change is difficult, nobody wants to do that if not must, so it feels dbs are not ready still in 2022. What’s your opinion on this?