We are planning to have one long running workflow per account that orchestrates a whole bunch of ‘workflows’ based on the requests it receives. As part of this ‘orchestration’ is essentially creating a whole bunch of queues through workflow goroutines that listen to signals. This is a noob question but what are the consequences/trade offs that happen when a workflow has say 20+ goroutines running.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Event Loop and concurrency | 1 | 120 | November 1, 2024 | |
| What happens to signals sent to a closing workflow? | 4 | 1688 | June 2, 2023 | |
| Is workflow.Go safe for concurrency? | 13 | 3056 | April 22, 2025 | |
| Long-Running workflow, memory exhaustion, and parameter passing | 2 | 1905 | November 30, 2020 | |
| Design for coordinator workflow with potentially large history | 2 | 953 | August 31, 2021 |