Completed
We can't put the world into a transaction
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Six Little Lines of Fail
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 6 little, innocuous lines of code
- 3 Failure is ALWAYS an option
- 4 is probably not good for business
- 5 We can't put the world into a transaction
- 6 Assume failures
- 7 Plan for the worst
- 8 4 options for dealing with failures between two systems
- 9 The Master Plan
- 10 For each external resource, examine possibilities and pick best option based on business requirements
- 11 First up: Stripe
- 12 Probably don't want to ignore a failed payment
- 13 Retry
- 14 Undo
- 15 Not unless we want duplicate emails
- 16 We can't un-send emails
- 17 Finally: RabbitMQ
- 18 Can't un-send a message
- 19 Compensating message is... weird
- 20 Coordinate
- 21 Taking a step back
- 22 Can we avoid exceptions by breaking the process coupling?
- 23 Way too much going on in a single button click
- 24 Modern ecommerce uses background processing to fulfill orders
- 25 Starting the workflow
- 26 Routing slip
- 27 Saga pattern
- 28 Process manager pattern
- 29 Orchestration or choreography?