Unless your CI is configured to do so, it won't be able to follow the action of deploying both Lambda functions. This is a simple example of the complexity that a monorepo could introduce to your build system.
To address this, we may need to package the date-util and publish it into a package registry so that each Lambda can refer to a particular version. However, requiring a separate CI/CD pipeline to publish this package also adds another level of complexity.
These modifications introduce another problem: the CI should be intelligent enough to determine the dependency order and build the dependencies in order. Besides, non-dependent components in the code base could run in parallel to reduce the overall build duration. Yet, this would also add more complexity to the overall build system.
Once you set up a complicated list of workflows, handling dependencies, versions, etc., whenever the application gets modified, your build system becomes a bottleneck and could become fragile. Therefore, you may need modern tools and tech to address these challenges.
#cicd-setup #lambda-functions #dependency-management #monorepo-complexity #modern-tools-for-build-systems
[
Collection
]
[
|
...
]