The Vitess 8.0 Documentation
making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore. For reference, please refer to the diagram below: Note: A VStream is distinct from a VStreamer were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow multiple indexes per table, and there are many types of indexes. Extending destination databases, while the application is still pointing to the source database as the primary datastore. • Create custom tools to backfill old data from the source to destination system. VReplication0 码力 | 331 页 | 1.35 MB | 1 年前3The Vitess 6.0 Documentation
making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore. For reference, please refer to the diagram below: Note: A VStream is distinct from a VStreamer were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow you to define multiple indexes per table, and there are many types0 码力 | 210 页 | 846.79 KB | 1 年前3The Vitess 7.0 Documentation
making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore. For reference, please refer to the diagram below: Note: A VStream is distinct from a VStreamer were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow you to define multiple indexes per table, and there are many types0 码力 | 254 页 | 949.63 KB | 1 年前3The Vitess 9.0 Documentation
making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore. For reference, please refer to the diagram below: Note: A VStream is distinct from a VStreamer were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow multiple indexes per table, and there are many types of indexes. Extending destination databases, while the application is still pointing to the source database as the primary datastore. • Create custom tools to backfill old data from the source to destination system. VReplication0 码力 | 417 页 | 2.96 MB | 1 年前3The Vitess 11.0 Documentation
making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore. For reference, please refer to the diagram below: Figure 1: VStream diagram Note: A VStream were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow multiple indexes per table, and there are many types of indexes. Extending destination databases, while the application is still pointing to the source database as the primary datastore. • Create custom tools to backfill old data from the source to destination system. VReplication0 码力 | 481 页 | 3.14 MB | 1 年前3The Vitess 10.0 Documentation
making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore. For reference, please refer to the diagram below: Note: A VStream is distinct from a VStreamer were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow multiple indexes per table, and there are many types of indexes. Extending destination databases, while the application is still pointing to the source database as the primary datastore. • Create custom tools to backfill old data from the source to destination system. VReplication0 码力 | 455 页 | 3.07 MB | 1 年前3The Vitess 12.0 Documentation
making it a convenient tool to feed a CDC (Change Data Capture) process downstream from your Vitess datastore. For reference, please refer to the diagram below: Note: A VStream is distinct from a VStreamer were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow multiple indexes per table, and there are many types of indexes. Extending destination databases, while the application is still pointing to the source database as the primary datastore. • Create custom tools to backfill old data from the source to destination system. VReplication0 码力 | 534 页 | 3.32 MB | 1 年前3The Vitess 5.0 Documentation
were to draw an analogy, the indexes in a database would be the equivalent of the key in a NoSQL datastore, except that databases allow you to define multiple indexes per table, and there are many types0 码力 | 206 页 | 875.06 KB | 1 年前3
共 8 条
- 1