This ticket encompasses researching potential implementations for a mailserver integrated with the auth microservice. The requirements/questions of this ticket include:
- Is it feasible to build our own simple SMTP server? Is this too large of a commitment, worth the time? If so, what are some of the technologies we could integrate into the codebase (keeping in mind our DDD-inspired organization)?
- What free/low-cost alternatives exist for an SMTP server? Is introducing an external dependency worth the efficiency it will bring? How easy is it to work with?
- What sort of templating capabilities/styling customization do either of the above options entail? Would it be easy to generate email templates for the following purposes:
- Confirming the email of a new Waterloo student on account creation.
- Emailing dynamic updates on followed content.
- Resetting users' passwords on request.
- How would other use-cases in the auth microservice communicate with the mail-server? Is this something we want to be accessible to Waterpark via an API (Waterpark does not support it's own mailserver)?
Here's the corresponding Notion spike to summarize research and offer a recommendation/development guidelines.
This ticket encompasses researching potential implementations for a mailserver integrated with the auth microservice. The requirements/questions of this ticket include:
Here's the corresponding Notion spike to summarize research and offer a recommendation/development guidelines.