We will now bootstrap the project using the Serverless CLI. As we have seen, a service is considered as the building block of the infrastructure. Each service has got infrastructural components and the code for function(s). Serverless doesn't enforce any opinions on how to the structure constituent services together apart from it having a serverless.yaml file in the root of the service. Developers are free to structure the project in any way they see fit, as per their use cases and their preference of granularity. Please note that every service that is created corresponds to a single API gateway in the AWS Infrastructure. This means that in a nanoservice infrastructure, each function becomes a service that is deployed ...
Bootstrapping the project
Get Hands-On Serverless Applications with Kotlin now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
