You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 12, 2024. It is now read-only.
|[**Data Branching®**](/docs/concepts/data-branching)| Included |
69
69
70
70
\* Production branch storage is billed at $1.50 (1 primary + 2 replicas) and development branch storage is billed at $0.50 (1 primary).
71
71
@@ -150,7 +150,9 @@ When you choose to change cluster size, we upgrade each of your replicas one by
150
150
151
151
## PlanetScale Enterprise plan
152
152
153
-
PlanetScale's Enterprise Plan is great for users that want to scale farther, shard horizontally, and run PlanetScale in a dedicated AWS/GCP account. We offer many different deployment options, all of which come with the same set of standard features. The table below covers those shared features, as well as the different options that vary depending on your chosen deployment.
153
+
PlanetScale's Enterprise Plan is great for large-scale businesses who require the enterprise-level SLAs, want expert assistance through enterprise support, and would prefer to run in your own AWS or GCP account.
154
+
155
+
We offer many different deployment options, all of which come with the same set of standard features. The table below covers those shared features, as well as the different options that vary depending on your chosen deployment.
@@ -168,13 +170,12 @@ If you’re not sure whether your use case requires an Enterprise plan, we’re
168
170
169
171
In general, if you need any of the following, Enterprise may be the best solution for you:
170
172
171
-
- Resource-based pricing
172
-
- Unlimited connections
173
-
- Elegant sharding solution
174
-
- Enhanced support — our expert team becomes an extension of your own
173
+
- Enhanced support — our expert team becomes an extension of your own. Additional options for technical account management, Slack-based support, and phone escalation.
174
+
- You need additional support to horizontally shard and migrate your database(s) to PlanetScale
175
175
- You need your database deployed in a single-tenant environment
176
176
- You need to keep your data in **your own** AWS or GCP account
177
177
- You need a PCI DSS certified service provider
178
+
- Mission-critical [response times](/docs/support/support-overview#initial-response-times) including continuous support coverage
178
179
- Any other customizations — Our Enterprise plans offer a lot of flexibility, so if you have a requirement that’s not listed here, it’s best to [reach out](/contact) and we can see how we can help
Copy file name to clipboardExpand all lines: docs/concepts/what-is-planetscale.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: 'What is PlanetScale'
3
3
subtitle: 'Learn about what PlanetScale is, how it came to be, and how our unique features can help you scale and improve development speed.'
4
-
date: '2023-04-05'
4
+
date: '2024-09-23'
5
5
---
6
6
7
7
## What is PlanetScale
@@ -62,7 +62,7 @@ PlanetScale allows you to break up a monolithic database and partition the data
62
62
63
63
Another scenario that companies with massive databases often run into is connection limits due to MySQL. With PlanetScale, we can support [nearly infinite connections](/blog/one-million-connections). Vitess offers built-in [connection pooling](https://vitess.io/docs/reference/features/connection-pools/), and we've built our own [edge infrastructure](/blog/introducing-the-planetscale-serverless-driver-for-javascript) into PlanetScale to ensure connection limits are never an issue.
64
64
65
-
We generally recommend sharding when your database exceeds 250 GB of data. Sharding is offered on our [enterprise plans](/pricing). [Please reach out](/contact)for more information. If you decide you want to shard your database(s), our solutions team will work with you to come up with a sharding strategy.
65
+
We generally recommend exploring horizontal sharding when your database exceeds 250 GB of data and you are beginning to feel some of the [pains associated with large scale](/blog/how-to-scale-your-database-and-when-to-shard-mysql). [Sharding](/docs/concepts/cluster-configuration) is offered on our Scaler Pro plan (currently only supported for new tables). If you need assistance with with setting up horizontal sharding, migrating to PlanetScale, or want enterprise-level SLAs, we offer this through our [Enterprise plan](/enterprise) option. [Please reach out](/contact) for more information.
Copy file name to clipboardExpand all lines: docs/devops/the-operate-phase-of-devops.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: 'The Operate phase of the DevOps cycle'
3
3
subtitle: 'Where the operations team performs tasks to keep the application online.'
4
-
date: '2023-03-13'
4
+
date: '2024-09-23'
5
5
---
6
6
7
7
Now that everything is deployed into production and confirmed working, the operations team's main focus is keeping everything online. Ideally, this is done with a system that will monitor application load to detect spikes in usage and automatically scale resources up to keep up with the traffic. This can be accomplished with platforms like EC2 in AWS, but also on-premise with Kubernetes.
@@ -22,7 +22,7 @@ One thing that can be overlooked is the fact that backups are pointless if the d
22
22
23
23
### Horizontal scaling
24
24
25
-
PlanetScale is built in [Vitess](https://vitess.io), which is an open-source project that enables horizontal scaling for MySQL databases. If you are in the Enterprise tier, you have additional configuration options available to horizontally scale your database, further reducing the load on individual nodes as well as increasing performance and resiliency.
25
+
PlanetScale is built in [Vitess](https://vitess.io), which is an open-source project that enables horizontal scaling for MySQL databases. [Sharding](/docs/concepts/cluster-configuration), available on our Scaler Pro plan, further reducing the load on individual nodes as well as increasing performance and resiliency.
You can see the [PlanetScale airbyte-source README](https://github.com/planetscale/airbyte-source/blob/main/README.md) for more details on these options.
Copy file name to clipboardExpand all lines: docs/sharding/overview.md
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: 'Sharding with PlanetScale'
3
3
subtitle: 'Learn how PlanetScale can help you horizontally scale your MySQL database with our sharding solution.'
4
-
date: '2024-09-20'
4
+
date: '2024-09-23'
5
5
---
6
6
7
7
{% callout %}
@@ -35,8 +35,7 @@ When you're at the point where you've maxed out your vertical scaling efforts an
35
35
36
36
## How does our sharding process work?
37
37
38
-
When it comes time to shard your database, we recommend following our [sharding quickstart](/docs/sharding/sharding-quickstart) guide. You may also
39
-
contact our [Technical Solutions team](/contact) to identify the best [sharding scheme](https://vitess.io/docs/reference/features/sharding/#sharding-scheme) for your database.
38
+
When it comes time to shard your database, we recommend following our [sharding quickstart](/docs/sharding/sharding-quickstart) guide. If you need assistance identifying the best [sharding scheme](https://vitess.io/docs/reference/features/sharding/#sharding-scheme) for your database, or are interested in expert-level support, our [Enterprise plan](/enterprise) may be a better option for you. [Get in touch](/contact) for more information.
40
39
41
40
PlanetScale uses an explicit sharding system.
42
41
This means that, if you are going to horizontally shard your data, we have to tell Vitess which sharding strategy to use for each sharded table.
Copy file name to clipboardExpand all lines: docs/sharding/sequence-tables.md
+1-5Lines changed: 1 addition & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,9 @@
2
2
title: 'Sequence Tables'
3
3
subtitle: 'Learn how to create sequence tables on a sharded PlanetScale database.'
4
4
label: 'Enterprise'
5
-
date: '2024-08-29'
5
+
date: '2024-09-23'
6
6
---
7
7
8
-
{% callout %}
9
-
This feature is only available on our [Enterprise plan](/docs/concepts/planetscale-plans#planetscale-enterprise-plan). If you'd like more information about how we can help you shard your MySQL database, [get in touch](/contact).
10
-
{% /callout %}
11
-
12
8
In MySQL, it is common to have an integer primary key that uses the `AUTO_INCREMENT` feature for assigning IDs.
13
9
However, if you have a horizontally-sharded table, you will not be able to use `AUTO_INCREMENT` for your ID.
14
10
In such a setup, the rows of the table are distributed across many instances of MySQL.
0 commit comments