Timeline for Microservices: Handling eventual consistency
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 1, 2018 at 14:04 | comment | added | Laiv | That said, for this specific scenario (password change notification), I agreed with this approach. As soon as it suites the requirements. | |
| Feb 1, 2018 at 14:00 | comment | added | Laiv |
If you can send the email at the beginning then your approach is fine. If you have to send something alongside with the email. Maybe a sort of link/data that only can be obtained after the consistency is achieved, then you can not send the email first. That is what I commented as consider asking the organization first.. You are likely right. However, I have found to be important to condition those events we cannot be undo. For example notifications to the end-user. Notification lying on the real state of the user's data might case a bad impression.
|
|
| Feb 1, 2018 at 13:48 | history | edited | Laiv | CC BY-SA 3.0 |
added 5 characters in body
|
| Feb 1, 2018 at 11:15 | history | answered | ctrl-alt-delor | CC BY-SA 3.0 |