Open k-allagbe opened 9 months ago
@rngadam please review this and let me know if this corresponds to your original idea for decoupling email sending from membrane-backend.
@k-allagbe
We'll have to make a decision on how to schedule jobs / execute jobs. So far candidates are:
I would make the pubsub and event notification through websocket a future feature in its own ticket, for now it's sufficient just to have a REST /api interface to query (for polling).
Also, please produce a diagram to accompany your ticket (as per internal diagram documentation). you can include pubsub/websocket in there too.
Currently email sending is a feature of membrane-backend only. We want to make it a standalone microservice. It would offer http and websocket interfaces. It would receive and write email requests and parameters to a postgresql database. A job would then routinely send the enqueued emails. Confirmations will then be returned to the caller services via websocket.