Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

Commit

Permalink
Update 01-Overview.md
Browse files Browse the repository at this point in the history
  • Loading branch information
nikolasburk authored Mar 5, 2018
1 parent d92dd17 commit 4709e2c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/1.3/04-Reference/05-Clusters/01-Overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Prisma services are deployed to so-called _clusters_. A cluster is a hosted envi
In essence, there are two kinds of _clusters_ you can deploy your Prisma service to:

- **Self-hosted / local clusters**: Self-hosted (or locally deployed) clusters are running on [Docker](https://www.docker.com). They are created and managed using the Prisma CLI which governs the underlying Docker _images_ and _containers_ for you.
- **Development clusters** (based on Prisma Cloud): Development clusters allow to conventiently deploy your Prisma service to the web without the overhead of configuring your own cluster. Note that development clusters have certain limitations, such as rate limiting of incoming requests (max 10 requests per 10 seconds) and an upperbound in storage capacity (100 MB).
- **Development clusters** (based on Prisma Cloud): Development clusters allow to conventiently deploy your Prisma service to the web without the overhead of configuring your own cluster. Note that development clusters have certain limitations, such as rate limiting of incoming requests (max 10 requests per 10 seconds) and an upper bound in storage capacity (100 MB).

> For the vast majority of use cases, **self-hosted clusters are the preferred option to deploy Prisma services**. This chapter explains how to create and manage your own self-hosted clusters.
Expand Down

0 comments on commit 4709e2c

Please sign in to comment.