A new column is never just a field. It is a structural decision, a modification that alters queries, indexes, and migrations. Whether in SQL, NoSQL, or a hybrid store, extending a schema means touching the foundation. Done well, it is a clean extension. Done poorly, it can fracture performance and raise maintenance costs.
In relational databases, adding a new column involves both schema updates and considerations for existing rows. Nullable defaults may prevent downtime, but they also introduce ambiguity. Non-null columns demand backfilling, which can lock tables and block reads. For high-traffic systems, online schema change tools like gh-ost or pt-online-schema-change let you push updates without halting operations.
In NoSQL systems, a new column often means adding a new key to documents or rows. The schema flexibility reduces friction, but query patterns can suffer if indexes do not adapt. Search performance depends on updating all associated indexes and ensuring data validation is in place.