Pygeoapi by default supports both sync and async modes for process execution. Our execute process, which executes an invest model, can take an arbitrarily long time to complete. While the pygeoapi server seems to be ok with this (did not time out after 5+ minutes), we'll likely run into timeouts in other components. Specifically, the maximum allowed request timeout for API Gateway is 600 seconds. And synchronous execution is really not the right pattern that our API clients should be using, given the widely varying runtime of invest models.
Pygeoapi by default supports both sync and async modes for process execution. Our
executeprocess, which executes an invest model, can take an arbitrarily long time to complete. While the pygeoapi server seems to be ok with this (did not time out after 5+ minutes), we'll likely run into timeouts in other components. Specifically, the maximum allowed request timeout for API Gateway is 600 seconds. And synchronous execution is really not the right pattern that our API clients should be using, given the widely varying runtime of invest models.