Django web plus Celery workers plus beat. Should these be three process groups in one app, or separate apps?
Solved
Solved by rhea
Three process groups in one app is the common setup: they share the image and secrets, and you scale each one independently with lark scale count web=2 worker=1 beat=1. Keep exactly one beat.
Jump to post166 views · 2 likes · 2 users
Related topics
Suggested topics
- Rails 8 solid_queue on Larkhost: one pod or two?1 reply
- The back porch: what are you running on a single shared-cpu pod?3 replies
- Python 3.13 images are now the default for new launches2 replies
- Node.js app memory climbs until OOM — only on Larkhost2 replies
- Laravel queues stop processing after a deploy1 reply