Learn AWS Serverless Computing

Service

The last layer is where the service abstractions are written. For maximum code reuse, these are likely to be libraries that you can reuse in other functions where you need to interact with the same service. For example, you might write a library that interacts with DynamoDB tables in a way that is specific to your problem domain. This is also the place to write bespoke integrations with other systems that the function might interact with, such as a CRM system or SOAP-based service.

A good idea would be to create Lambda layers from these so that they can be imported with ease when they're needed.

So, where does the business logic go? Well, that really depends on the language you're using, but, as a guide, it can exist anywhere outside ...