I got jumped on for the “no connections” thing. It’s more about instantiating connections and understanding how functions scale (concurrency, cold starts) and then imagining what would happen under different load scenarios.

You *can* store some state inside a Lambda 😲 and use a cache (I have seen it!) but most of the time it’s best to store state in a data store that is very quick to connect/disconnect on-demand and can rapidly scale e.g. DynamoDB. This usually means it’s not an RDBMS (or at least, not the way it’s usually used).

Written by

ServerlessDays CoFounder (Jeff), ex AWS Serverless Snr DA, experienced CTO/Interim, Startups, Entrepreneur, Techie, Geek and Christian

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store