51249b59eb
## What changed? This centralizes the health checker into `health.SignalAggregator`. This standardizes how we will do health checks by using latency based quantiles and error ratios. The goal is to be able to use this for any spot we want to do health detection. Main idea is you have your overall settings and thresholds for latency metrics and error ratios, then you can have "groups" of specific keys that have their own tracking for latency and error ratios. For grpc health checking, these keys will be the endpoints. For something like history the keys will be the specific functions. Doing this also sets us up better for per namespace health settings. This is 1 of 3 prs. This one is mainly for just testing that everything works as expected. Then next one will be cleaning up and consolidating all the health signals in the health package. Then the last one will be applying ## Why? We need more strict settings/thresholds for endpoints we consider to be critical like StartWorkflowExecution, SignalWorkflowExecution, StartActivityExecution, etc... ## How did you test it? - [x] built - [ ] run locally and tested manually - [x] covered by existing tests - [x] added new unit test(s) - [x] added new functional test(s) ## Potential risks Currently, if you pass in bad settings (e.g. buffer size <= 0), there will be panics. This isn't a newly introduced problem, but it is an existing one that will be addressed in future PRs.
Temporal—durable execution platform
Introduction • Getting Started • Contributing • Temporal Docs • Temporal 101
Introduction
Temporal is a durable execution platform that enables developers to build scalable applications without sacrificing productivity or reliability. The Temporal server executes units of application logic called Workflows in a resilient manner that automatically handles intermittent failures, and retries failed operations.
Temporal is a mature technology that originated as a fork of Uber's Cadence. It is developed by Temporal Technologies, a startup by the creators of Cadence.
Getting Started
Download and Start Temporal Server Locally
Execute the following commands to start a pre-built image along with all the dependencies.
brew install temporal
temporal server start-dev
Refer to Temporal CLI documentation for more installation options.
Run the Samples
Clone or download samples for Go or Java and run them with the local Temporal server. We have a number of HelloWorld type scenarios available, as well as more advanced ones. Note that the sets of samples are currently different between Go and Java.
Use CLI
Use Temporal CLI to interact with the running Temporal server.
temporal operator namespace list
temporal workflow list
Use Temporal Web UI
Try Temporal Web UI by opening http://localhost:8233 for viewing your sample workflows executing on Temporal.
Repository
This repository contains the source code of the Temporal server. To implement Workflows, Activities and Workers, use one of the supported languages.
Contributing
We'd love your help in making Temporal great.
Helpful links to get started:
- work on or propose a new feature
- learn about the Temporal Server architecture
- learn how to build and run the Temporal Server locally
- learn about Temporal Server testing tools and best practices
- join the Temporal community forum and Slack