-
Couldn't load subscription status.
- Fork 3
Improve Restate Server deployment docs #60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Next batch of comments 😅
| --- | ||
|
|
||
|
|
||
| Restate can run as a single binary, making it easy to run it on a variety of platforms, from your local machine, to a VM, to Kubernetes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Restate can run as a single binary, making it easy to run it on a variety of platforms, from your local machine, to a VM, to Kubernetes. | |
| Restate is distributed as a single binary that implements all features required to run a single- or multi-node cluster, making it easy to run it on a variety of platforms, from your local machine, to a VM, to Kubernetes. |
|
|
||
| <Card icon={"cloud"} href={"/cloud/getting-started"} title={"The easiest way to run Restate is with Restate Cloud."}> | ||
| Keep deploying your code the same way you do now. | ||
| Restate Cloud handles resilience, observability, and scalability for your code, with no additional infra. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Restate Cloud handles resilience, observability, and scalability for your code, with no additional infra. | |
| Restate Cloud handles resilience, observability, and scalability for your code, with no additional infrastructure to manage beyond your services. | |
| Pair Restate Cloud with a serverless compute provider for the simplest operational experience. |
|
|
||
| ## Compute | ||
|
|
||
| The easiest way to deploy and manage the Restate cluster and services is via the [Kubernetes operator](/server/deploy/kubernetes), since it gives you a lot of built-in functionality and tooling for deploying services, versioning, and more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The easiest way to deploy and manage the Restate cluster and services is via the [Kubernetes operator](/server/deploy/kubernetes), since it gives you a lot of built-in functionality and tooling for deploying services, versioning, and more. | |
| The easiest way to deploy and manage a Restate cluster and containerized Restate services is via the [Kubernetes operator](/server/deploy/kubernetes), as it provides the simplest experience for deploying Restate clusters, deploying services while managing versioning, and more. |
| This approach is also recommended for single-node Restate deployments because it will make managing the persistent volume of your Restate instance easier. | ||
| If your instance goes down, the Kubernetes provider automatically restarts it and reattaches the persistent volume. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| This approach is also recommended for single-node Restate deployments because it will make managing the persistent volume of your Restate instance easier. | |
| If your instance goes down, the Kubernetes provider automatically restarts it and reattaches the persistent volume. | |
| This approach is great even for single-node Restate deployments because it makes managing the Restate node much simpler, handling node restarts or Restate version updates with ease. Kubernetes is responsible for keeping the Restate container running and, crucially, makes sure that the persistent volume attachment follows it around if it moves between nodes. |
| -e RESTATE_CLOUD_REGION \ | ||
| -p 8080:8080 \ | ||
| -p 9090:9090 \ | ||
| -p 9070:9070 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not part of your changes, but spotted a missing slash here:
| -p 9070:9070 \ |
Co-authored-by: Pavel Tcholakov <pcholakov@gmail.com>
No description provided.