News for hackers. Stuff that matters.

A comment on Sample cloud-native application with microservices. Parent comment

Re:Sample cloud-native application with microservices by jbarham on Thursday February 14, 2019 @10:20PM (#19168209)
Yes, 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.

[ Parent | on HN ]
Re:Sample cloud-native application with microservices by jsmeaton on Friday February 15, 2019 @02:42AM (#19169190)
A 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.

[ Parent | on HN ]
Re:Sample cloud-native application with microservices by jbarham on Friday February 15, 2019 @04:20AM (#19169561)
I 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.

[ Parent | on HN ]
Re:Sample cloud-native application with microservices by kumaraman on Thursday February 14, 2019 @10:34PM (#19168260)
That 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.
[ Parent | on HN ]