Monorepo serverless workflows break across multiple apps
Developers with several serverless apps or functions in one repository run into provider workflows that assume a single app, require separate local processes or ports, or make deployment configuration awkward to share. The evidence shows workarounds such as duplicating configuration and package files, plus at least one developer switching platforms; it does not establish how common the problem is today.
For developers maintaining serverless monorepos. Mentioned from Apr 2017 to Dec 2023 on GitHub and Hacker News.
7 different people described this problem in 5 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.3/10
- Frequency
- 7.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I suppose my expectation as I added a couple more function apps was that I'd be able to, say, right-click deploy to each one in the tree
With this framework, I need to run each cloud function on a separate port, which can become quite a hassle as the number of functions increase. How will multiple Cloud Functions be better supported going forward?
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks