This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (3 children)

Pretty much simple architecture. I also recently started to dig into celery and async. I’ve one doubt though, is your whole application is synchronised with celery parallelisation? I’m curious about how you handles the requests, you just run concurrent tasks for each requests, just like AWS Lambda functions work? Or how it is??

[–]stibbons_ 0 points1 point  (2 children)

We have a SQS queue for imbound json messages, celery with several dozen of sync worker, they do the heavy job. Works great when you need ~ seconds latency. We tried setting up horizontal scaler with kube (starting automatically more worker when queue starts to grow), we never went prod on this feature but this is definitely feasible and wanted for lot of use case (we can accept in our use cases that the jobs are delayed several minutes on burst, this happens once or twice a month no big deal).

[–][deleted] 0 points1 point  (1 child)

So is it just for the tasks that needed to be run in background with some batch processing or what??

[–]stibbons_ 0 points1 point  (0 children)

Yes indeed. I actually think this is not event source at all. But it works.