AWS Lambda

Many people are moving to utilizing Function as a Service (FaaS) offerings to deploy their applications to the cloud. How do we take advantage of the benefits of FaaS while mitigating the risks associated with vendor lockin? What if we want to deploy across multiple cloud providers? In this post, I will be discussing how to isolate your vendor dependencies in a boundary layer when writing serverless applications.

When deploying serverless applications to AWS Lambda, do you create a single, monolithic function to handle all the application endpoints or a lambda function per endpoint? In this post, I will explore these two approaches to deploying serverless applications.