Glossary
Every term the courses use, defined in one line and then in a paragraph. Written to be read out of order.
Showing 3 of 3 matching “Migration”
A recorded, ordered change to your data’s shape.
A versioned schema change applied identically in every environment. Needed because code can be rolled back in seconds and data cannot. Safe changes expand first, then contract days later.
The declared shape of your data.
Which tables exist, which columns they have, and what is allowed in them. Changing it is a migration. In schemaless databases the schema still exists, just in your code instead of the database.
Running old and new API shapes side by side.
Offering /v1 and /v2 so existing callers keep working while new ones use the new shape. The same expand-then-contract idea as a safe schema migration, applied to an API.
See also Breaking change, Deprecation