. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Making Schema Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . position. A single VStream can also consolidate change events from multiple shards in a keyspace, making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore should now return an empty result: sudo aa-status | grep mysqld If this doesn’t work, you can try making sure all lurking processes are shutdown, and then restart the example again in the /tmp directory:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466 Making Schema Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . position. A single VStream can also consolidate change events from multiple shards in a keyspace, making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore should now return an empty result: sudo aa-status | grep mysqld If this doesn’t work, you can try making sure all lurking processes are shutdown, and then restart the example again in the /tmp directory:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Making Schema Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . position. A single VStream can also consolidate change events from multiple shards in a keyspace, making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore should now return an empty result: sudo aa-status | grep mysqld If this doesn’t work, you can try making sure all lurking processes are shutdown, and then restart the example again in the /tmp directory:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 Making Schema Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . position. A single VStream can also consolidate change events from multiple shards in a keyspace, making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore should now return an empty result: sudo aa-status | grep mysqld If this doesn’t work, you can try making sure all lurking processes are shutdown, and then restart the example again in the /tmp directory:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Making Schema Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . position. A single VStream can also consolidate change events from multiple shards in a keyspace, making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore should now return an empty result: sudo aa-status | grep mysqld If this doesn’t work, you can try making sure all lurking processes are shutdown, and then restart the example again in the /tmp directory:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Making Schema Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . should now return an empty result: sudo aa-status | grep mysqld If this doesn’t work, you can try making sure all lurking processes are shutdown, and then restart the example again in the /tmp directory: "type": "sequence" }, "product": {} } } Vindexes The next decision is about the sharding keys, aka Primary Vindexes. This is a complex decision that involves the following considerations: • What are the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Making Schema Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . position. A single VStream can also consolidate change events from multiple shards in a keyspace, making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore should now return an empty result: sudo aa-status | grep mysqld If this doesn’t work, you can try making sure all lurking processes are shutdown, and then restart the example again in the /tmp directory:

isomorphism, heterogeneous language and cloud native. Apache ShardingSphere aiming at reasonably making full use of the computation and storage capacity of existed database in distributed system, rather Introduction 1.1.1 ShardingSphere-JDBC ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra service at Java JDBC layer. With the client end connecting directly to the kinds of ORM frameworks. 1 Apache ShardingSphere document, v5.0.0-beta • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template or direct use of JDBC. •

document, v5.0.0 1.1.1 ShardingSphere-JDBC ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra services at the Java JDBC layer. With the client end connecting directly to which is fully compatible with JDBC and all kinds of ORM frameworks. • Applicable in any ORM framework based on JDBC, such as JPA, Hibernate, Mybatis, Spring JDBC Template or direct use of JDBC. • predecessor of Apache ShardingSphere, ShardingSphere‐JDBC defines itself as a lightweight Java framework that provides extra service at Java JDBC layer. With the client end con‐ necting directly to the

technical—business expectations have grown, putting additional pressure on data teams to enable faster decision-making and drive tangible value. Business lines, customers and consumers now demand and expect: Faster interpret, and extract value from data. Together, they enable efficient data processing, enhance decision-making, and improve user experiences: Analytics transforms raw data into actionable insights through enhancing discoverability, accelerating decision-making, and improving operational efficiency. AI acts as the intelligence layer, optimizing both search and analytics by making them faster, smarter, and more intuitive