Getting to know Temporal

Temporal Co-Founder and CEO, Maxim Fateev, and Head of Product, Ryland Goldstein, discuss how Temporal works, provide a walkthrough of the history of Temporal, and give an in-depth product demo.

00:00 Intro
01:17 Understanding what Temporal solves
07:37 How Temporal was born
12:06 Creating the right developer experience
15:41 Product demo led by Maxim Fateev
27:21 Customer use cases
32:40 What is durable execution?
33:44 How to get started with Temporal
35:03 Thanks for watching!

---

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

Learn more

Developer resources

[softdevstuff]

I cannot unsee this. Changes everything. Too good.

[JohnMcclaned]

shh, stop telling everyone about temporal, it's a competitive advantage.

[bartlettpsj]

Getting more interested in Temporal now I've got the teeshirt. Temporal seems more programmer first in that Workflows are defined in code. Many other Workflow (older?) products tend to use a UX or some form of configuration file (e.g. XML). Are there plans to have the ability to configure workflows through a UI, and then you just write the activities?

[suraj_yadav_]

Hi Max,
Its good to hear how temporal orchestrate the whole intense task by retrying it and reaches to the satisfactory output.
But as you highlight temporal is the middleware for different process of Organization to execute there task. One thing I wanted to understand is like how you try to gain the companies confidence on sending any data that passes through your channel like there could be scenarios where confidential data needs to be send via the activity but how will you give a confidence to the companies that this data will never be leaked?

[wangyongt]

How to compare it with Azure Logic Apps? Which is much simpler and the author can fully focus on the business logic

[RavikumarMooli]

I had a usecase in which checking for sufficient information to perform next activity but if it fails it needs to go parent workflow how should i do it using temporal

[gahshunker]

so when the worker with the updated code is re-run, it won't repeat the steps that successfully already have been completed, and just go on from where the previous failure was? that's poggers. what happens if some of the code in the "successfull" part of the already completed workflow slightly was changed, along with the bug fix? will temporal pick that up and repeat the successfull steps?

[maf_aka]

I guess I'm missing something, but doesn't this create a single point of failure?

[nonefvnfvnjnjnjevjenjvonej]

Don't retriable jobs aka sidekiq in rails also solve this problem? Can you kindly explain what Temporal provides in addition to that?

[_sudipidus_]

Andy Dufrense has come a long way after escaping shawshwank :P

[dragondeviento]

LOL 3.5 year "A lifetime, a life time" LOL this is just so F funny