forked from docs/doc-exports
Hasko, Vladimir
a5cc543164
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com> Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
25 lines
3.6 KiB
HTML
25 lines
3.6 KiB
HTML
<a name="ddm_01_0001"></a><a name="ddm_01_0001"></a>
|
|
|
|
<h1 class="topictitle1">Overview</h1>
|
|
<div id="body1553068858234"><div class="section" id="ddm_01_0001__section168015434812"><h4 class="sectiontitle">Definition</h4><p id="ddm_01_0001__p816643132816">Distributed Database Middleware (DDM) is a MySQL-compatible, distributed middleware service designed for relational databases. It can resolve distributed scaling issues to break through capacity and performance bottlenecks of databases, helping handle highly concurrent access to massive volumes of data.</p>
|
|
<p id="ddm_01_0001__p95658982">DDM uses a decoupled compute and storage architecture and provides functions such as database and table sharding, read/write splitting, elastic scaling, and sustainable O&M. Management of instance nodes has no impacts on your workloads. You can perform O&M on your databases and read and write data from and to them on the DDM console, just like as operating a single-node MySQL database.</p>
|
|
</div>
|
|
<div class="section" id="ddm_01_0001__section1584010111191"><h4 class="sectiontitle">Advantages</h4><ul id="ddm_01_0001__ul11346175571214"><li id="ddm_01_0001__li0346165571213">Automatic Database and Table Sharding<p id="ddm_01_0001__p2842172023012"><a name="ddm_01_0001__li0346165571213"></a><a name="li0346165571213"></a>MySQL databases are usually deployed on single nodes. Once a fault occurs, all data may be lost, and your workloads are 100% affected.</p>
|
|
<p id="ddm_01_0001__p135031321101312">DDM supports automatic database and table sharding to distribute data across multiple data nodes, so impacts on your services are greatly reduced once a fault occurs. It also supports explosive growth of services.</p>
|
|
</li><li id="ddm_01_0001__li1334635571211">Read/Write Splitting<p id="ddm_01_0001__p135531540141319"><a name="ddm_01_0001__li1334635571211"></a><a name="li1334635571211"></a>DDM can leverage data nodes. If there is still great query pressure after horizontal sharding, you can enable read/write splitting to speed up database processing and access, without the need to reconstruct your service system.</p>
|
|
</li><li id="ddm_01_0001__li434685541217">Elastic Scaling<p id="ddm_01_0001__p567418380312"><a name="ddm_01_0001__li434685541217"></a><a name="li434685541217"></a>MySQL databases can support only medium- and small-scale service systems because their CPU, memory, and network processing are limited by server configurations and their storage depends on the size of SSD or EVS disks.</p>
|
|
<p id="ddm_01_0001__p18800655121315">DDM supports both compute and storage scaling. You can add nodes to a DDM instance or scale up its node class. Alternatively, increase shards or data nodes to distribute data from one large table to multiple tables or scale out storage resources as services grow, without worrying about O&M.</p>
|
|
</li></ul>
|
|
</div>
|
|
<div class="section" id="ddm_01_0001__section936394811218"><h4 class="sectiontitle">Service Architecture</h4><div class="fignone" id="ddm_01_0001__fig3955117193215"><span class="figcap"><b>Figure 1 </b>DDM service architecture</span><br><span><img id="ddm_01_0001__image6734109191910" src="en-us_image_0000001733266537.png"></span></div>
|
|
</div>
|
|
<div class="section" id="ddm_01_0001__section84661023152410"><h4 class="sectiontitle">How DDM Works</h4><div class="fignone" id="ddm_01_0001__fig646622362415"><span class="figcap"><b>Figure 2 </b>DDM working diagram</span><br><span><img id="ddm_01_0001__image84665238242" src="en-us_image_0000001685307354.png"></span></div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_01_0000.html">Service Overview</a></div>
|
|
</div>
|
|
</div>
|
|
|