6 ms·
Sorry to say mate but maybe... I’d usually pop that on a queue and get a separate service to pick it up... maybe that’s what you’re doing?
by holografix 8y ago
Sorry to say mate but maybe... I’d usually pop that on a queue and get a separate service to pick it up... maybe that’s what you’re doing?
- zorga 8y agoEmail is already a queue.
- jbarham 8y agoYes, I send emails async using Django-RQ (previously Celery). It's still a one-liner once you've configured your async task handler. Which makes the example custom email sending microservice even more ridiculous when it can be done trivially by configuring proven off-the-shelf components and third party email delivery services.
- kumaraman 8y agoThat works well in your current situation, but when you have multiple products and services that also need to send emails it makes sense to combine them into a single service.
- jsmeaton 8y agoA bit off topic (sorry) but how are you finding django-rq compared to celery? Anything you miss? Anything you gained? I wasn’t sure how ready rq was for prime time, but I’ve hit far too many celery bugs and the maintenance hasn’t been great for awhile.
- jbarham 8y agoI found Django-RQ far simpler to configure than Celery. Given that I'm using Redis for caching anyway, it also removed RabbitMQ as a dependency which Celery basically requires. Django-RQ's job decorator is basically a drop-in replacement for Celery's task decorator. Django-RQ's built-in Django admin app is very nice. My Celery usage was pretty simple (mostly background email sending and PDF generation) but for those use-cases Django-RQ has been a very good replacement. Your mileage may vary of course.