Hi, i am challenged to develop an effective failover mechanism of aggregated notification of certain transactions. I have transactions by merchant.
Every hour i need to send email (and some other) notifications, aggregated by the merchants to specific recipients. Now i am doing it with "github.com/jasonlvhit/gocron" which runs hourly and selects all transactions where date added > date of last worker run. Then i fire "github.com/pocke/goevent", signed method prepares the email and sends it over. What i doubt here is if the worker will fail at certain point of time, and notifications wont be ever sent for that transactions, so i need to create some workaround with logging of all transactions which were successfully sent (notified). it happens to be non efficient and not clear. is there any pattern how to implement such kind of notifications with failover? Worth to add, that there are huge amount of transactions, so adding some column with a flag "notifiication_sent" wont work (because there are couple of different notifications and becasue modifying table with transactions is not a good idea). Same as storing the log is not good idea because it will be another table with even more records NumberOfTransaction*NumberOfNotificationTypes. thank you for an advice. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
