@@ -79,7 +79,12 @@ performance closely as you increase the number of routers. If you see
79
79
performance degradation, it may be beneficial to cap the number of
80
80
:binary:`~bin.mongos` routers in your deployment.
81
81
82
- .. include:: /images/sharded-cluster-production-architecture.rst
82
+ The following diagram shows a common sharded cluster architecture used
83
+ in production:
84
+
85
+ .. image:: /images/sharded-cluster-production-architecture.png
86
+ :alt: Diagram that shows a production-level sharded cluster
87
+ containing multiple shards and mongos routers.
83
88
84
89
Development Configuration
85
90
-------------------------
@@ -88,14 +93,19 @@ For testing and development, you can deploy a sharded cluster with a
88
93
minimum number of components. These **non-production** clusters have the
89
94
following components:
90
95
91
- - A replica set :ref:`config server <sharding-config-server>` with one
92
- member.
96
+ - One :binary:`~bin.mongos` instance.
93
97
94
- - At least one shard as a single-member :term:`replica set`.
98
+ - A single shard :term:`replica set`.
95
99
96
- - One :binary:`~bin.mongos` instance.
100
+ - A replica set :ref:`config server <sharding-config-server>`.
101
+
102
+
103
+ The following diagram shows a sharded cluster architecture used for
104
+ **development only**:
97
105
98
- .. include:: /images/sharded-cluster-test-architecture.rst
106
+ .. image:: /images/sharded-cluster-test-architecture.png
107
+ :alt: Diagram that shows a development sharded cluster
108
+ containing a single shard and mongos router.
99
109
100
110
.. warning:: Use the test cluster architecture for testing and
101
111
development only.
0 commit comments