-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
복기(celery 브로커로 redis를 택한 이유) & celery를 택한 이유 #144
Labels
Comments
rabbitmq
|
redis
|
결론
아쉬운점
|
안정성을 위한 Timeout
|
그럼 왜 celery 라이브러리를 활용했는가?
그럼 celery는 어떻게 동작하는가?
|
skarltjr
changed the title
복기(celery 브로커로 redis를 택한 이유)
복기(celery 브로커로 redis를 택한 이유) & celery를 택한 이유
Feb 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: