@Adam Ralph one small question: i don't understand when+where the Saga code that updates the state in the DB runs? i assume its when the Handle method is called but i don't see a call to the Base class (Saga)'s methods, except for the Send method that i assume only sends ProcessOrder message and doesn't deal with the DB.
@Adam Ralph thanks, that's good info. i'm still a bit confused though. from the link u sent: "Saga state is read just before Handle is invoked and written immediately after Handle is completed". i just don't understand how this technically happens. how the Saga code is executed. in the discount example in DiscountingTests.cs we call the Handle method (discounting.Handle(...)). i just don't see how the Saga code is executed at that point and when i debug this method call the Handle method in Discounting.cs is called immediately. what am i missing here? maybe because it's just a small example (without DB integration) the Saga code isn't executed but in a complete project (with DB integration) it is executed. if u have such a complete project/example (with SQL server integration) that u can share that would be great. thanks.
@Adam Ralph thanks but its not a question for a discussion forum either since it will just confuse people into thinking there is something wrong with NServiceBus or something. if u can read my question and have a short answer here it would be great. if u can direct me to / share a complete project/example with SQL server integration that's great as well.
Best explanation of saga time travel
Great Presentation! can u please share the code u demoed or another full code example of the Saga pattern
@Adam Ralph thanks but the link is broken
@Adam Ralph Works now. thanks
@Adam Ralph one small question: i don't understand when+where the Saga code that updates the state in the DB runs? i assume its when the Handle method is called but i don't see a call to the Base class (Saga)'s methods, except for the Send method that i assume only sends ProcessOrder message and doesn't deal with the DB.
@Adam Ralph thanks, that's good info. i'm still a bit confused though.
from the link u sent: "Saga state is read just before Handle is invoked and written immediately after Handle is completed".
i just don't understand how this technically happens. how the Saga code is executed.
in the discount example in DiscountingTests.cs we call the Handle method (discounting.Handle(...)).
i just don't see how the Saga code is executed at that point and when i debug this method call the Handle method in Discounting.cs is called immediately. what am i missing here? maybe because it's just a small example (without DB integration) the Saga code isn't executed but in a complete project (with DB integration) it is executed. if u have such a complete project/example (with SQL server integration) that u can share that would be great. thanks.
@Adam Ralph thanks but its not a question for a discussion forum either since it will just confuse people into thinking there is something wrong with NServiceBus or something.
if u can read my question and have a short answer here it would be great. if u can direct me to / share a complete project/example with SQL server integration that's great as well.
I do not really understand the problem.
He seems to imply the discount should be applied based on information sent to the client BEFORE the order is actually placed.