Half of my project is being developed in serverless (the microservices) that add to the big monolith application.
I've basically implemented a "monorepo CI/CD" which mostly works fine for our needs. (With some limitations/bugs in Gitlab CI due to the monorepo design)
For the most part we probably don't get so many functions bundled together, thus avoiding the deployment limitations referred.
Only one serverless app is reaching any kind of limits (200 resources per Cloudformation template if I remember correctly)
Yeah that makes sense. That's basically how Seed started. Thanks for sharing.
What we started noticing with teams that we were talking to (and our own experience) was that the build process started limiting our architecture choices. For example, we want functions packaged individually because it reduces cold starts. But because the builds take long we had to make a trade-off. And that didn't make sense to us.
Half of my project is being developed in serverless (the microservices) that add to the big monolith application.
I've basically implemented a "monorepo CI/CD" which mostly works fine for our needs. (With some limitations/bugs in Gitlab CI due to the monorepo design)
For the most part we probably don't get so many functions bundled together, thus avoiding the deployment limitations referred.
Only one serverless app is reaching any kind of limits (200 resources per Cloudformation template if I remember correctly)
https://pedrogomes.medium.com/gitlab-ci-cd-serverless-monore...