|
12 | 12 | :depth: 2
|
13 | 13 | :class: onecol
|
14 | 14 |
|
15 |
| - |
16 | 15 | When deploying your database, you must choose between deploying to a single region or multiple regions. The following diagram
|
17 | 16 | shows these options, which are explained further below:
|
18 | 17 |
|
19 |
| -:ref:`Single-Region Deployment<arch-center-paradigms-single>` |
20 |
| - |
21 |
| -This is the simplest deployment option. In a single-region deployment, your |
22 |
| -data is stored in one of a provider's regions (such as AWS's ``us-west-2`` |
23 |
| -or Google's ``asia-northeast3``). With this simplicity and lower cost comes |
24 |
| -the risk of lower availability and potentially lower latency, depending on the |
25 |
| -distribution of your application's users. |
26 |
| - |
27 |
| -:ref:`Multi-Region Deployment <arch-center-paradigms-multi-region>` |
28 |
| - |
29 |
| -This deployment paradigm provides a more robust option with higher availability. |
30 |
| -There are several types of multi-region deployments: |
31 |
| - |
32 |
| -- Deploying clusters to multiple regions hosted by a _single_ cloud provider |
33 |
| - within a single "geography" (large areas like a continent or countries). |
34 |
| - For example, you deploy clusters in regions called ``us-1`` and ``us-3``, |
35 |
| - both of which are in the United States and are managed by the same cloud |
36 |
| - provider. |
37 |
| - |
38 |
| -- Deploying clusters to one or more regions in two or more geographies. |
39 |
| - For example, you deploy clusters in regions called ``us-1`` and ``us-3``, |
40 |
| - both of which are in the United States, and a third cluster in ``eu-2``, |
41 |
| - which is in Europe. |
42 |
| - |
43 |
| -- Deploying clusters to multiple regions hosted by _multiple_ cloud providers. |
44 |
| - For example, you deploy clusters in the AWS region ``us-west-1`` and the GCP |
45 |
| - region ``us-east4``. |
46 |
| - |
47 |
| - |
48 |
| -:ref:`Global Deployment <arch-center-paradigms-global>` |
49 |
| - |
50 |
| - This option should be considered for only the most complex situations; for |
51 |
| - example, where you need global aggregation of user data, or where legal terms |
52 |
| - dictate specific hosting requirements. |
53 |
| - |
54 |
| -The following diagram shows these options: |
55 |
| - |
56 | 18 | .. figure:: /includes/images/deployment-types.png
|
57 | 19 | :figwidth: 750px
|
58 | 20 | :alt: An image showing the different deployment options.
|
|
0 commit comments