Skip to content

Commit

Permalink
Clarify development clusters for Starter vs Enterprise (#3248)
Browse files Browse the repository at this point in the history
* Clarify development clusters for Starter vs Enterprise

* Edits based on Aaron's message

* Apply suggestions from code review

Add edits

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* Update next docs

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
  • Loading branch information
jprcoliveira and github-actions[bot] authored Feb 14, 2024
1 parent 55250fc commit 55dbaba
Show file tree
Hide file tree
Showing 2 changed files with 34 additions and 18 deletions.
26 changes: 17 additions & 9 deletions docs/components/concepts/clusters.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: "Learn more about the clusters available in your Camunda 8 plan."

A [cluster](../../guides/create-cluster.md) is a provided group of production-ready nodes that run Camunda 8.

- **Enterprise** plan customers can create as many production or development clusters as they want.
- **Enterprise** plan customers can create as many production or development clusters as they want based on their Enterprise agreement.
- **Starter** plan customers are limited based on the [fair usage limits of the plan](https://camunda.com/legal/fair-usage-limits-for-starter-plan/).

Production clusters come in three sizes: small (S), medium (M), and large (L). To learn more about the size of cluster best suited for your use case, refer to our [Best Practices](/components/best-practices/best-practices-overview.md) for more information on [sizing your runtime environment](/components/best-practices/architecture/sizing-your-environment.md#sizing-your-runtime-environment).
Expand All @@ -32,19 +32,27 @@ When your Free Trial plan expires, you are automatically transferred to the Free

## Development clusters

Development clusters are recommended for development, testing, proof of concepts, and demos.
Development clusters, available in the Starter and Enterprise plans, are recommended for development, testing, proof of concepts, and demos.

Starter Plan users have one **development cluster**, with free execution for development included in their plan. Deployment and execution of models (process instances, decision instances, and task users) is provided at no cost.
The way this type of cluster works varies depending on if you are using it in the Starter or the Enterprise plan.

Additional clusters can be purchased through your [billing reservations](/components/console/manage-plan/update-billing-reservations.md).
### Development clusters in the Enterprise Plan

Additionally, the following applies to **development clusters**:
Enterprise Plan users can purchase development clusters as part of their Enterprise subscription agreement. Deployment and execution of models (process instances, decision instances, and task users) are included at no extra cost for this type of cluster. Additionally, this type of cluster in the Enterprise plan follows the [standard data retention policy](/docs/components/concepts/data-retention.md) and does not auto-pause when not in use.

- **Cluster is not high-available & less hardware**: Reduced hardware resources and availability compared to production cluster (for example, one Zeebe node only).
- **Shorter history of processes and decisions**: Data retention in Operate, Optimize, and Tasklist is reduced to one day. For example, pending or historical process instances are deleted after one day.
Please [contact us](https://camunda.com/contact/) if you are an existing customer and would like to purchase a development cluster.

:::caution
### Development clusters in the Starter Plan

**Cluster auto-pause** is not yet available. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality will work, including BPMN timers and BPMN message catch events.
Starter Plan users have one **development cluster** with free execution for development included in their plan. Deployment and execution of models (process instances, decision instances, and task users) are provided at no cost.

Additional clusters can be purchased through your [billing reservations](/components/console/manage-plan/update-billing-reservations.md).

Additionally in the Starter Plan, the following applies to **development clusters**:

- **Cluster is not highly available & includes less hardware**: Reduced hardware resources and availability compared to production cluster (for example, one Zeebe node only).
- **Shorter history of processes and decisions**: Data retention in Operate, Optimize, and Tasklist is reduced to one day. For example, pending or historical process instances are deleted after one day as per the [fair usage limits of the Starter plan](https://camunda.com/legal/fair-usage-limits-for-starter-plan/).

:::caution
**Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality will be limited, including the execution of BPMN timers and BPMN message catch events.
:::
26 changes: 17 additions & 9 deletions versioned_docs/version-8.4/components/concepts/clusters.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: "Learn more about the clusters available in your Camunda 8 plan."

A [cluster](../../guides/create-cluster.md) is a provided group of production-ready nodes that run Camunda 8.

- **Enterprise** plan customers can create as many production or development clusters as they want.
- **Enterprise** plan customers can create as many production or development clusters as they want based on their Enterprise agreement.
- **Starter** plan customers are limited based on the [fair usage limits of the plan](https://camunda.com/legal/fair-usage-limits-for-starter-plan/).

Production clusters come in three sizes: small (S), medium (M), and large (L). To learn more about the size of cluster best suited for your use case, refer to our [Best Practices](/components/best-practices/best-practices-overview.md) for more information on [sizing your runtime environment](/components/best-practices/architecture/sizing-your-environment.md#sizing-your-runtime-environment).
Expand All @@ -32,19 +32,27 @@ When your Free Trial plan expires, you are automatically transferred to the Free

## Development clusters

Development clusters are recommended for development, testing, proof of concepts, and demos.
Development clusters, available in the Starter and Enterprise plans, are recommended for development, testing, proof of concepts, and demos.

Starter Plan users have one **development cluster**, with free execution for development included in their plan. Deployment and execution of models (process instances, decision instances, and task users) is provided at no cost.
The way this type of cluster works varies depending on if you are using it in the Starter or the Enterprise plan.

Additional clusters can be purchased through your [billing reservations](/components/console/manage-plan/update-billing-reservations.md).
### Development clusters in the Enterprise Plan

Additionally, the following applies to **development clusters**:
Enterprise Plan users can purchase development clusters as part of their Enterprise subscription agreement. Deployment and execution of models (process instances, decision instances, and task users) are included at no extra cost for this type of cluster. Additionally, this type of cluster in the Enterprise plan follows the [standard data retention policy](/docs/components/concepts/data-retention.md) and does not auto-pause when not in use.

- **Cluster is not high-available & less hardware**: Reduced hardware resources and availability compared to production cluster (for example, one Zeebe node only).
- **Shorter history of processes and decisions**: Data retention in Operate, Optimize, and Tasklist is reduced to one day. For example, pending or historical process instances are deleted after one day.
Please [contact us](https://camunda.com/contact/) if you are an existing customer and would like to purchase a development cluster.

:::caution
### Development clusters in the Starter Plan

**Cluster auto-pause** is not yet available. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality will work, including BPMN timers and BPMN message catch events.
Starter Plan users have one **development cluster** with free execution for development included in their plan. Deployment and execution of models (process instances, decision instances, and task users) are provided at no cost.

Additional clusters can be purchased through your [billing reservations](/components/console/manage-plan/update-billing-reservations.md).

Additionally in the Starter Plan, the following applies to **development clusters**:

- **Cluster is not highly available & includes less hardware**: Reduced hardware resources and availability compared to production cluster (for example, one Zeebe node only).
- **Shorter history of processes and decisions**: Data retention in Operate, Optimize, and Tasklist is reduced to one day. For example, pending or historical process instances are deleted after one day as per the [fair usage limits of the Starter plan](https://camunda.com/legal/fair-usage-limits-for-starter-plan/).

:::caution
**Cluster auto-pause** is not yet available and only applies to non-Enterprise clusters. Development clusters will be paused if they go unused for two hours. When a cluster is paused, not all functionality will be limited, including the execution of BPMN timers and BPMN message catch events.
:::

0 comments on commit 55dbaba

Please sign in to comment.