最新消息:20210816 当前crifan.com域名已被污染,为防止失联,请关注(页面右下角的)公众号

[整理]Flask中后台任务队列库:Celery vs RQ

Flask crifan 5272浏览 0评论

折腾:

[已解决]Flask中添加后台进程用于提醒到期时发送通知

期间,想要搞清楚:

Celery 和RQ

到底区别在哪

自己到底选哪个

flask Celery vs RQ

What is the difference between RQ (redis queue) and Celery? – Quora

“Celery is a very advanced async task delegation and processing system. It can use redis as one of many supported transport sytems (message queue). It also supports or will support languages other than Python.

Redis queue is a much simpler async task processor that only uses redis as the message queue.

If your requirements are very simple like fire off an email when a user signs up then you can probably use redis queue. If you are planning on building something big where you need greater flexibility and control over you tasks then go for celery.

That said, there is no reason why you can’t use celery for simpler tasks as well. It has a good history, very vibrant community and is being developed very actively. Also, if you choose celery, it’ll be easier to scale out later if needed.”

Getting Started — Celery 3.1.23 documentation

Introducing RQ » nvie.com

Task Queues – Full Stack Python

最后决定使用:

更简单方便的RQ。

[后记]

flask Redis Queue

结果除了之前搜到的:

又看到了:

别人把RQ集成到Flask

mattupstate/flask-rq: RQ (Redis Queue) integration for Flask applications

然后的然后,又有人在Flask-RQ的基础上再次封装了:

Flask-RQ2 — Flask-RQ2 16.0.2 documentation

jezdez/Flask-RQ2: A Flask extension for RQ.

Flask-RQ Flask-RQ2

转载请注明:在路上 » [整理]Flask中后台任务队列库:Celery vs RQ

发表我的评论
取消评论

表情

Hi,您需要填写昵称和邮箱!

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址
82 queries in 0.268 seconds, using 22.19MB memory