Please enable JavaScript.
Coggle requires JavaScript to display documents.
Shema Migrations, image, image, image, image - Coggle Diagram
Shema Migrations
Key Points
Secure schemes can be migrated to version-controlled sequence
Databases without schema need migration
Schema-less databases can use any migration technique
Databases without schema can read schema changes and use incremental migration
Schema Changes in a NoSQL Data Store
Incremental Migration
Two ways
Convert existing data to the new schema
Ensure that before changing schema, data can be analyzed and saved in the new schema(Incremental Migration)
Migrating data over time
Transition period in the changes
Migrations in Graph Databases
The edges in these databases have types and properties
Changing a data type of an edge can render the system unusable
Migrate all database edges to keep the database up and running
Another option is to create new edges and delete the old ones at the same time.
Changing Aggregate Structure
Change the schematic design
RDBMS
Migrations in legacy proyects
Migration to existing applications
Extracting the structure in scripts and their code
No transactional data
Maintain compatibility
Migrations for green field proyects
Sequential scripting
Orderly migration
Version control repositories
Shema Changes
NoSql without schemas
Data changes with reduced friction
Improve developer productivity