As a suggestion, emitting a domain event like CommentCreated would be more effective when creating a comment. A handler, such as the MakeCommentCommandHandler, can then manage this event and attempt to send the email. This approach helps separate these two logics, adhering to the Single Responsibility Principle (SRP) and Open/Closed Principle (OCP). It also allows for more straightforward future extensions, such as sending notifications through other channels.

I noticed your project doesn't have authentication or authorization and I would like to implement them.
There a few questions that need to be answered :

• What type of auth would you prefer ? (JWT maybe?)
• Should we include authorization as well or do you think it's not required for this project ?

@thisisnabi

Hello, This is database diagram of blogger, I think that yellow marked fields should be primary keys of particular tables. because in this situation we can have multiple record with same data
like below!!

SubscriberId ArticleId Id
1111111111 2222222 1
1111111111 2222222 2
1111111111 2222222 3

It should be something like this

Or something like that

Hi @thisisnabi ,
Before anything, I want to thank you for your great repository.❤️ It's brilliant and I am learning a lot from it. 👍

I noticed the email service is not implemented and I would to like to develop this feature.
There are two main subjects that need to be discussed :

• The email address that we are going to send from
• The implementation itself (I was thinking about FluentEmail package but we could also do it from scratch)

What are your thoughts ?