News for hackers. Stuff that matters.
Re:Why Uber Engineering Switched from Postgres to MySQL by 1024core on Tuesday July 26, 2016 @11:07PM (#12170234)
So if the "send email" step fails (temporarily), the next worker to come along will grab the same receipt and send it again?

I think a better solution would be to use a centralized queue that actually does the mail sending, and retries in case of failure.

Re:Why Uber Engineering Switched from Postgres to MySQL by srd on Wednesday July 27, 2016 @02:03AM (#12170830)
That depends on the implementation of the queue. Most queues have a "failed/retry" concept, where they mark failed jobs to be retried in some set future point in time. So one failed job does not hold up your entire queue processing.
Re:Why Uber Engineering Switched from Postgres to MySQL by ChoHag on Wednesday July 27, 2016 @07:45AM (#12171995)
> a centralized queue that actually does the mail sending, and retries in case of failure.

A bit like SMTP?

Re:Why Uber Engineering Switched from Postgres to MySQL by lazyant on Wednesday July 27, 2016 @10:56AM (#12173305)
not necessarily, in the first write we can update receipt status as "queued" so queue system can update to "sent" or retry