Building event-driven, reactive applications with Temporal: Workflows vs Sagas

Dominik Tornow, Temporal Technologies

Many modern applications are implemented as event-driven, reactive applications. In this session we will compare choreography and sagas to orchestration and Temporal workflows when implementing event-driven applications. We will explore which approach provides the best reliability, the best scalability, lowest coupling of components, and a stellar developer experience.

Presented at Replay 2022
--

Temporal is the simple, scalable, open source way to write and run reliable cloud applications.

Learn more

Developer resources

[willalmur]

I don't get how during the time the slides were incorrect he just continued describing and elaborating on a the wrong concept. Especially two that are easy to distinguish apart. Even if they were copy pasted, he continued talking about choreography while saying "orchestration" until the audience pointed it out. That's some good separation of concerns.

[WendelSchultz]

The few slides following about 12:31 through 14:31 should have "Choreography" in the left box, is this correct? [UPDATE: he concedes as much at 15:01 or so. thanks]

Love this presentation. Thank you Dominik.

[giuliocasa]

Cool! Declarative and event-driven are not necessarily the best patterns.
Reminiscent of the good old approach to simulating imperative programming within the Haskell monad, or within F#'s context expression, or even Scala ZIO's typesafe for comprehension.

[KevinONeillPlus]

The presentation premiss is strong but the talk is poorly prepared (multiple incorrect slides). Dominick obviously knows the subject and has a lot to share, he just falls short here.