[WhyNotHugo]

I've worked with API servers that moved from a dedicated service to lambdas. We were using Django in this case, and just added a tiny wrapper that converts lambda>asgi (using Magum).

For local development, we continued using Django normally inside its own docker container with matching dependency versions and like.

[raydiatian]

Yeah I considered doing something like this but ultimately balked (maybe it was my inner prima dona) at the idea of needing to support undeployed adapter code (outside of Docker containers or build scripts), even if rarely. Might be easier with Python and Django, but the best typescript solutions I could come up required me to diverge from “normal-looking” express.js

[WhyNotHugo]

There is no undeployed adapter here. I use Django which exposes an asgi interface.

Traditionally, one would use something like Daphne as an HTTP<>asgi adapter. In my case, I use Magnum as a Lambda<>asgi adapter.

For development, I just use Django's build-in development server (which auto-reloads on code changes and alike).

So there's not "extra" code that's only used for development, and I really don't maintain any extra glue code myself either.