<story><title>Going Serverless: Migrating an Express App to AWS API Gateway and AWS Lambda</title><url>https://aws.amazon.com/blogs/compute/going-serverless-migrating-an-express-application-to-amazon-api-gateway-and-aws-lambda/</url></story><parent_chain></parent_chain><comment><author>falcolas</author><text>Serverless via Lambda has been, frankly, a disappointment so far. The benefit is that I&amp;#x27;m supposed to not have to manage servers anymore, yet I find myself, well, managing servers.&lt;p&gt;I have to build and assign IAM roles, subnets, set up application configuration files in fixed external services (since you can&amp;#x27;t do things like set environment variables), configure the endpoints in nginx^h^h^h^h^h API Gateway, suffer through cold starts, fight against arcane packaging issues with site directories and .pth files (though this is probably just be a Python thing), fight concurrency throttling, external timeouts, manage out-of-band database connections, logging which requires even more IAM permissions...&lt;p&gt;This doesn&amp;#x27;t even consider how many times I&amp;#x27;ve had to tear down and re-create an API Gateway setup because it got &amp;quot;stuck&amp;quot; and would stop working.&lt;p&gt;Finally, WTF is up with not being able to test API Gateway -&amp;gt; S3 integrations if the S3 bucket is in the same region as the gateway instance? It&amp;#x27;s a two plus year old bug by now, and a real pain (especially when coupled with other AWS services which require the bucket to be in the same region as the rest of a service - such as CodePipeline).&lt;p&gt;Perhaps it&amp;#x27;s just because I&amp;#x27;m familiar with setting up and provisioning servers, but for basic web services and periodic tasks, Lambda is much harder to work with most of the time. Its biggest benefit so far has been the low cost.</text></comment>
<story><title>Going Serverless: Migrating an Express App to AWS API Gateway and AWS Lambda</title><url>https://aws.amazon.com/blogs/compute/going-serverless-migrating-an-express-application-to-amazon-api-gateway-and-aws-lambda/</url></story><parent_chain></parent_chain><comment><author>Everhusk</author><text>I&amp;#x27;m always surprised at the lack of discussion around database connection reuse with AWS Lambda.&lt;p&gt;It&amp;#x27;s a pretty big deal that every single API call requires a new database connection. The only solutions I&amp;#x27;ve seen so far are to run a separate app to interface with the database, or moving the connection outside of the handler (which still has issues).&lt;p&gt;Am I missing something or is everyone just really happy to use DynamoDB?</text></comment>