I find the premise of this article (that a small maintenance outage is never acceptable) to be unreasonable for the vast majority of applications developed by the vast majority of developers.
If, as claimed, when using a RDBMS:
> your database will make the change almost immediately without having to update any rows
The amount of downtime required to deploy a change which renames the column and changes the code which accesses said column, is marginally more than "almost immediately".
I find the premise of this article (that a small maintenance outage is never acceptable) to be unreasonable for the vast majority of applications developed by the vast majority of developers.
If, as claimed, when using a RDBMS:
> your database will make the change almost immediately without having to update any rows
The amount of downtime required to deploy a change which renames the column and changes the code which accesses said column, is marginally more than "almost immediately".