4 ms·
For those people commenting here that don't seem to quite understand the point of a workflow library: It's for writing code that has steps that involve humans.
by jiggawatts 4y ago
For those people commenting here that don't seem to quite understand the point of a workflow library:
It's for writing code that has steps that involve humans. E.g.: sending a mail notification for someone to approve a document, that kind of thing.
These are inherently slow and asynchronous, because humans operate on timescales of hours or days, not milliseconds.
- lorendsr 4y agoTraditional workflow systems are often used for specific types of business processes, particularly those that are async like human-in-the-loop. Temporal, while it uses the "workflow" terminology, is a new type of thing. At a basic level, it's "do you want your backend code to run reliably?" If yes, and you're okay with the latency hit of each step getting persisted for you, then the answer is "use Temporal to write your backend code." It's a new programming model that lets you develop at a higher level of abstraction, where you don't have to be concerned about faults in the hardware or network or downstream services/3rd party APIs being temporarily down. Where you no longer have to code retries, timeouts, use task queues, or use a message bus to communicate between services. And oftentimes don't even need to use a database.