MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 8 · Error handling, faults and retries

Compensation, and its limits

Lesson 87 of 175 · 2 min

Undoing work already committed in another system. When it is possible, when it is theatre, and why designing to avoid needing it is cheaper. COMPENSATION IS NOT A ROLLBACK. A rollback removes the effect; compensation adds an opposing one. The original transaction stays, with its reversal beside it, and both are visible to anybody looking at the record afterwards. WHEN IT IS POSSIBLE: where the target offers a genuine inverse operation and the state has not moved on. A created record you can delete or void, a posting you can reverse. WHEN IT IS THEATRE, and this is the half worth knowing. When the effect has already left the system — a payment file sent to a bank, an email to a customer, a message to a partner. When the record has been used since: an invoice you would reverse has been paid, matched, or reported on. And when the…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 8 · Error handling, faults and retries

  1. 1The four kinds of failure
  2. 2Faults versus errorsFree preview
  3. 3Scope and fault handlers
  4. 4What to do with a caught fault
  5. 5Retry: how many, how far apart
  6. 6The dead letter, and who reads it
  7. 7Partial failure in a batch
  8. 8Compensation, and its limits
  9. 9Alerting a human
  10. 10Resubmission: doing it safely
  11. 11Errors that are not failures
  12. 12What breaks: five error-handling failures
  13. 13Lab briefing · Break it five ways