# Proposal + seeking champion: Composable promise concurrency management **URL:** \ **Category:** 💡 Ideas\ **Tags:** proposal\ **Created:** [March 28, 2021, 8:50am UTC](https://es.discourse.group/t/proposal-seeking-champion-composable-promise-concurrency-management/713 "2021-03-28T08:50:45Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![theScottyJam](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/thescottyjam/32/616_2.png) [@theScottyJam](https://es.discourse.group/u/theScottyJam)\ **Post date:** [March 28, 2021, 4:24pm UTC](https://es.discourse.group/t/proposal-seeking-champion-composable-promise-concurrency-management/713/2 "2021-03-28T16:24:42Z")
This ... is the feature I need, and didn't even know I needed. There have certainly been times where I've wanted to cap the number of active promises, to prevent sending out a gazillion REST requests or database queries at the same time. Sometimes this occurs in production code, and the amount of ugly (and potentially buggy) code I would have to put in to implement this properly is scary. Sometimes this occurs in a database-upgrade script where I'm not really inclined to do anything too complicated or depend on anything external, so I just throw together a very non-performant solution. This also provides a very easy solution for the whole sync-errors while setting up promises issues, as discussed at length [here](https://es.discourse.group/t/synchronous-exceptions-thrown-from-complex-expressions-create-abandoned-promises-solutions/663/51) (it might not be what the O.P. wanted in that thread, but it'll certainly make me happy). It's a very creative API too - I love how simple it feels, yet it has so much power. --- _[View the full topic](https://es.discourse.group/t/proposal-seeking-champion-composable-promise-concurrency-management/713)._