Applying the Saga Pattern • Caitie McCaffrey • GOTO 2015

This presentation made Saga's click for me. Nice one.

I wonder if this pattern (transaction idempotentcy) can be applied in financial world? Probably it will be more complex solution - if you for example do fund transfer, how would your system retry if transaction failed...Also how compensation will work?

Very good presentation, thank you

What techniques did you use to achieve idempotency in your scenarios? - Great talk!

Awesome Presentation. Very well explained . Thanks !!

came from redux-saga docs ... didn't understand

This didn't click last time I watched this, this time it's like I already understood the whole thing. When did I actually learn it lol.

Very clearly and thoroughly explained, thank you.

what a clear presentation!! Thanks to your talk, i figure out what saga pattern is and could imagine what redux-saga does. Thx again!!

Need to learn the Saga Pattern for my first developer job, and this video was certainly a superb starting point!
Seldom does new concepts click as fast and easily as this one did after watching your talk.


Thank you, Caitie!

So if I'm understanding correctly: in order for the Saga to survive the Coordinator dying, either the forward transaction or the compensating transaction must be idempotent. However in the example of email, neither seems to be the case. Obviously sending out the email is not idempotent, nor would I want to flood the customer's inbox with hundreds of "disregard the last email" messages if the compensating action needs to be retried.

cantik

Blown away!!! Thank you :)

Totally stupid question - how do you achieve idempotency when you are making a totally new car/hotel/flight booking? Wouldn't that be a POST request? a new entry in db of the remote service? and POST is not idempotent.

That was a great presentation, thank you Caitie

My english is terrible but she is great even for me all was understandably

Many thanks 👍👍👍👍

Looks like a great fan base here for her... God Save them!

Although it is a bit fast, and some background knowledge is assumed, it's a great presentation ... Thanks !!

I don't see the relationship between this and redux-saga, but hey I watched the full thing and maybe, later on, I might come back and laugh at how stupid I was :) great speech.

Ohohoho! Perfect explanation. Now I can do my homework )) I'll borrow a couple of your slides if you don't mind of course. Thx!

Great talk. I learnt some new things.

Great talk. Thx !

My Ears didn't breathe at all watching whole talk 😂

Two questions

1. The presenter says they are using Azure Service Bus as a log. How does this work? I don't understand how a queue would be a useful way to store log information.
2. They mention a "CP log", what does that mean in this context?

Fantastic.

So load data into big bucket and then, at leisure, process and parcel out to store. On fail, retry. This is similar to CQRS except with that the big bucket is kept around and considered to be the database.

nice explanation and slides. i'm wondering where is the saga state stored if it's not in SEC?

Jeez I was just trying to make ajax calls from my web page. Great talk though !

Smart!

this is a very amazing talk. Thankyou

0.75x speed is perfect!

Very good presentation! Thanks for sharing!

뭔말이냐이게

Excellent talk.

Cool this is workflows and is implemented in things like temporal in 2023. Still wish it were easier to implement but we’re getting there.

Wonmderful talk! Very articulate and the examples are excellent. Thanks for sharing this.

Nice talk, still valid in 2023. :)

Great presentation. Still relevant in 2023 👍

Awesome talk. Thanks for a great presentation

Thank u so much for this presentation. Still worth for watching in 2025 and so on

Great talk!

Great presentation. Still relevant in 2025 👍