search

ietf-tools / bibxml-service

Django-based Web service implementing IETF BibXML APIs
https://bib.ietf.org
BSD 3-Clause "New" or "Revised" License
17 stars 19 forks source link

Switch Celery result backend to Django ORM (potentially) #204

Open strogonoff opened 3 years ago

strogonoff commented 3 years ago

Currently, task status/result persists in Redis, but if we want dataset indexing task history to be more reliable/exist for longer we should persist it in PostgreSQL (using django-celery-results). This would also make it available using Django ORM, making it more convenient to query task status.

strogonoff commented 3 years ago

Downside is performance overhead, Redis may be faster and task status data is more or less ephemeral so hitting Postgres for it may not be warranted.

strogonoff commented 2 years ago

As of https://github.com/ietf-ribose/bibxml-service/commit/3c619642a61f4694c519be646106f93929d1f27b, we use ORM/DB to capture indexing outcome (one per indexing task), a bit more persistently than just in Redis backend for Celery.

rjsparks commented 2 years ago

Is this still under consideration?