✳flâneur — a map of the web's best reading

temporal/docs/architecture/history-service.md at main · temporalio/temporal

github.com · 2,361 words · saved by 1 readers

This page is an introduction to the History Service architecture and internal implementation. See Temporal overview for a system architecture overview placing this in context. The History Service handles two main types of request (gRPC) relating to an individual Workflow Execution: Requests originating from the User Application (Start / Cancel / Query / Update / Signal / Reset etc). Requests originating from Temporal Workers, on completion of a Workflow Task or Activity Task. A simplistic description of what the History Service does when handling these requests is: Determine the new History Events that the request implies, and append these to Workflow History. If the request implies that a Workflow or Activity Task should be created for the workflow, then add a Transfer Task in a History Service task queue, representing the task that must be added to Matching Service. Alternatively, if the request is a Worker reporting that the user workflow is blocked on a timer, then add a Timer Task

History Service This page is an introduction to the History Service architecture and internal implementation. See Temporal overview for a system architecture overview placing this in context. The History Service handles two main types of request (gRPC) relating to an individual Workflow Execution: Requests originating from the User Application (Start / Cancel / Query / Update / Signal / Reset etc). Requests originating from Temporal Workers , on completion of a Workflow Task or Activity Task. A simplistic description of what the History Service does when handling these requests is: Determine t

Explore this link on the map →

related reading