We are using microrepos, we implement all logic in libraries then import those libs into another project that wraps it w/ the lambda logic. The lambda logic ten

We are using microrepos, we implement all logic in libraries then import those libs into another project that wraps it w/ the lambda logic. The lambda logic tends to be small and all the 'work' is done in libraries. Thought here being if we need to migrate to another serverless solution (or server solution) it's quick/easy to wrap the tested libraries in whatever the next logic should be. Then we use Apigee a127 Node project to invoke the lambda's. This is where authentication is done (we use Auth0 JWT/Bearer tokens). The Apigee a127 project invokes the lambda and handles routing. We looked at serverless but didn't want to use API Gateway since we already had apigee. We plan to look at SAM next but so far haven't need it. We have a few grunt scripts that we can use for running the lambda locally so far not a big deal. For logging we use an AWS ElasticSearch cluster and Kibana. So far we haven't run into any big issues with lambda, we see better response times when there is a constant load on the system, I guess that helps w/ keeping the lambda's warm. Even cold start isn't a big issue b/c the $$$ saved is well worth it. Automate EVERYTHING. You will quickly get a bunch of lambda's and you need a way to keep them all updated, manual SUCKS.