forked from docs/doc-exports
Wang , Deng Ke
ba65944bfd
Reviewed-by: Boka, Ladislav <ladislav.boka@t-systems.com> Co-authored-by: Wang , Deng Ke <wangdengke2@huawei.com> Co-committed-by: Wang , Deng Ke <wangdengke2@huawei.com>
16 lines
1.4 KiB
HTML
16 lines
1.4 KiB
HTML
<a name="dds_01_0025"></a><a name="dds_01_0025"></a>
|
|
|
|
<h1 class="topictitle1">Single Node Architecture</h1>
|
|
<div id="body1524735072535"><p id="dds_01_0025__p16172345183814">A single node instance, as its name suggests, contains only one node which can be accessed directly.</p>
|
|
<p id="dds_01_0025__p34524004112">As a supplement to the cluster and replica set architectures, the single-node architecture applies to R&D, testing, and non-core data storage of enterprises. While not as robust as replica sets, the single node architecture can be a less expensive way to visualize O&M and provide elastic scaling.</p>
|
|
<div class="note" id="dds_01_0025__note1658561782711"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="dds_01_0025__p742382512270">A driver handles all interactions between your application and the database in a language appropriate to the application. For details, see <a href="https://docs.mongodb.com/drivers/" target="_blank" rel="noopener noreferrer">official documents</a>.</p>
|
|
</div></div>
|
|
<div class="fignone" id="dds_01_0025__fig127610919118"><span class="figcap"><b>Figure 1 </b>Single node architecture</span><br><span><img id="dds_01_0025__image57779121115" src="en-us_image_0000001143053863.png"></span></div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="dds_01_0021.html">System Architecture</a></div>
|
|
</div>
|
|
</div>
|
|
|