. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4 Running Modes 11 4.1 Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2 Cluster . . . . . . . . . . . . 546 13.1.1 MODE What is the difference between standalone mode Standalone and Com- patible_Standalone? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 13.1.2 and BASE transac‐ tions, ShardingSphere provides distributed transaction capabilities on top of standalone databases, enabling data security across underlying data sources. Re ad /w ri te S pl it ti

1.3.2 Running Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Standalone mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Cluster mode . v5.2.0 1.3.2 Running Modes Apache ShardingSphere provides two running modes: standalone mode and cluster mode. Standalone mode It can achieve data persistence in terms of metadata information such as 2.5 Application Scenarios The database’s transactions can meet ACID business requirements in a standalone application scenario. However, in distributed scenarios, traditional database solutions cannot

Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.4.1 Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.4.2 Cluster Mode and BASE trans‐ actions, ShardingSphere provides distributed transaction capabilities on top of standalone databases, enabling data security across underlying data sources. Read/write Split‐ ting Read/write 2.1 1.4 Running Modes Apache ShardingSphere provides two running modes: standalone mode and cluster mode. 1.4.1 Standalone Mode It can achieve data persistence in terms of metadata information such

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4 Running Modes 11 4.1 Standalone Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2 Cluster and BASE transac‐ tions, ShardingSphere provides distributed transaction capabilities on top of standalone databases, enabling data security across underlying data sources. Re ad /w ri te S pl it ti Architecture 10 4 Running Modes Apache ShardingSphere provides two running modes: standalone mode and cluster mode. 4.1 Standalone Mode It can achieve data persistence in terms of metadata information such

ctx=acc&id=trs if you are hearing impaired. vi Chapter 1 MySQL Installer for Windows MySQL Installer is a standalone application designed to ease the complexity of installing and configuring MySQL products that run C:\ProgramData folders. The following table describes the files and folders that define MySQL Installer as a standalone application. Note Installed MySQL products are neither altered nor removed when you update or C:\ProgramData\MySQL \MySQL Installer for Windows\Manifest Product Cache The Product Cache folder contains all standalone .msi files bundled with the full package or downloaded afterward. C:\ProgramData\MySQL \MySQL

2 Memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Standalone mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.4 Cluster mode integration function testing. This is the default mode of Apache ShardingSphere. 3.2.3 Standalone mode Suitable in a standalone environment, through which data sources, rules, and metadata can be per‐ sisted use cost. Built‐in transaction managers have already been able to provide services through jar packages. Integrated with Apache ShardingSphere, it can guarantee the high con‐ sistency in cross‐database

2 Memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Standalone mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.4 Cluster mode integration function testing. This is the default mode of Apache ShardingSphere. 3.2.3 Standalone mode Suitable in a standalone environment, through which data sources, rules, and metadata can be per‐ sisted use cost. Built‐in transaction managers have already been able to provide services through jar packages. Integrated with Apache ShardingSphere, it can guarantee the high con‐ sistency in cross‐database

2 Memory mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2.3 Standalone mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 i 3.2.4 Cluster mode integration function testing. This is the default mode of Apache ShardingSphere. 3.2.3 Standalone mode Suitable in a standalone environment, through which data sources, rules, and metadata can be per‐ sisted use cost. Built‐in transaction managers have already been able to provide services through jar packages. Integrated with Apache ShardingSphere, it can guarantee the high con‐ sistency in cross‐database

................................................................................595 24.3.6.1. Standalone Hot Backups ....................................................................595 24.3.6.2. Compressed .................................................................................924 34.46. sql_packages ............................................................................................... .............................................................................3059 J.2.3. Debian Packages..............................................................................................3059

................................................................................562 24.3.6.1. Standalone Hot Backups .............................................................562 24.3.6.2. Compressed .................................................................................872 34.46. sql_packages ............................................................................................... .............................................................................2884 J.2.3. Debian Packages.......................................................................................2885 J.2.4