We're doing both stream processing and small query APIs using Lambda. A few pointers (from relatively short experience): - The best UC for Lambda seems to be

We're doing both stream processing and small query APIs using Lambda. A few pointers (from relatively short experience): - The best UC for Lambda seems to be stream processing where latency due to start up times is not an issue - For user/application-facing logic the major issue seems to be start-up-times (esp. JVM startup times when doing Java or your API gets called very rarely) and API Gateway configuration management using infrastructure as code tools (I'd be interested in good hints about this, especially concerning interface changes) - The programming model is very simple and nice but it seems to make most sense to split each API over multiple lambdas to keep them as small as possible or use some serverless framework to make managing the whole app more easy - This goes without saying, but be sure to use CI and do not deploy local builds (native binary deps)