Timeline for How to handle database connection drops?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10, 2020 at 17:10 | comment | added | Doc Brown | @Bharel: the approach presented here has a name: it is called "making write operations idempotent". If one calls this a "canned pattern" or not is pretty irrelevant. | |
| Aug 10, 2020 at 16:21 | comment | added | Berin Loritsch | Right. You need to be able to trace if your message was handled or not, and the only consistent identifier for that purpose would be the message id. The solution outlined above allows for message ids to be reused, but scopes the query well enough that if there is any implicit locking, it remains a record lock. | |
| Aug 10, 2020 at 14:29 | comment | added | Bharel | It doesn't happen frequently, but on a distributed system with lots of services, it can happen frequently enough to justify the need for a solution. Your statement saying there is no canned pattern, is exactly what I was looking for. Message IDs are not always feasible but are the only solution I guess. Thank you! | |
| Aug 10, 2020 at 14:25 | vote | accept | Bharel | ||
| Aug 10, 2020 at 14:03 | history | answered | Berin Loritsch | CC BY-SA 4.0 |