Talk about design using SNS, SQS. Why shipping has three services running etc.
Goal of Microservice is do one thing. This implies many small services and small databases. Sometime data between services out of synch due to one service is down, infrastructure outage etc.
Each receiver is guaranteed to receive one same message.
One receiver receives one unique message. No two receivers receive the same message.
Talk about new requirement. Send shipping confirmation email.
Talk about the limitation of Java Mail. It sends email but doesn’t detect the response that might be sent by receiver’s ISP.
Talk about what can be done SNS + SQS + SES. The system can be proactive with SES.
https://forums.aws.amazon.com/thread.jspa?threadID=150255
“
Presently we have this limitation to ensure that all email originating from Amazon SES is trustworthy -- in the sense that if SES sends an email from an email address, you can trust that SES has verified that the owner controls that email address. This deters spam and phishing and helps encourage legitimate use. Consequently we currently require all of the email addresses that you send from to be verified.
“