- Más nuevo
- Más votos
- Más comentarios
Yes your understanding is correct (and we should probably make it more clear in the docs). App Runner is optimized for request/response application (e.g. web servers, api services). We do indeed throttle CPU when no inbound requests are detected (and hence not served). App Runner would not be ideal (at least for now) to run worker type of processes. For that use case, if you are looking at something as simple as App Runner, the closest would be Copilot. Note Copilot is a multi-function CLI that allows you to deploy to App Runner as well as to ECS/Fargate via a set of built-in services patterns which includes web and worker services. The main difference between deploying to App Runner Vs ECS/Fargate is that in the latter case the resources (tasks, LBs, etc) are deployed in your account (whereas in AppRunner all the building blocks are deployed in an AWS account).
We are looking at expanding the type of workloads that App Runner can support in the future.
HTH
Hi @mreferre, Do you have any updates perhaps on the possibility of running worker processes op Apprunner?
Hi
We are currently setting up various services with AppRunner. We also need some workers for scheduled tasks and queues. These are not started via incoming requests, but via a scheduler that runs within the application.
Are there any best practices or AppRunner functions for this? Or is another tool more suitable for these tasks? Ideally, we can still use our application, as it already contains all the logic.
Thank you and best regards
Contenido relevante
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 3 años
Thanks for the response. It is a bit disappointing that this is the case since I really liked the simplicity of App Runner. If there was at least the option to prevent the throttling that would at least allow for customers to run a worker service even if they did not get any auto-scaling with it. I'll take a look at these other services that you mention to do what I need.
I hear your disappointment. Would you mind opening an issue on the public App Runner roadmap about this feature? Thanks!
Done: https://github.com/aws/apprunner-roadmap/issues/96