Developers are very familar with using abstractions to avoid having to write common, low-level interfaces for things like databases, messaging or interacting with APIs. Temporal abstracts away the tedious, low-level code that is always needed to ensure resiliency when interacting with external processes or APIs that might fail or take a long time to respond. By using straightforward SDKs available in the most popular language frameworks, developers can use Temporal to apply policy-based approaches to retrying calls that might fail due to failed connections or rate-limits so that the right things happen on a consistent basis. Temporal also takes care of the complexities of managing long-running processes where something needs to happen in the future whether that is minutes, days or months down the road. If your app needs to initiate a process that requires some human interaction (approvals, uploads, certifications, etc), Temporal tracks those human-in-the-loop interactions and automatically advances the process to the next step when ready. Temporal Cloud provides managed Temporal infrastructure so that you can not only get started quickly , but also can avoid the challenges of operating more self-hosted infrastructure. The Temporal UI and APIs provide robust troubleshooting and auditing capabilities so that you can see at a glance or investigate in great detail what is happening with your business procesess. Temporal is not workflow as many of us experienced it in the past (heavy XML standards, pretty diagrams that were hard to customize). Workflows and activities in Temporal are just code that leverages Temporal SDKs to abstract away the cruft of resiliency and reliability that every developer needs, but seldom wants to create from scratch.

The distributed running of activities as stubs to run in different workers is one good thing which we are glad using it.