Are we seeing the emergence of a generic software best practice of centralised state management emergence across the industry? This table based storage pattern

Are we seeing the emergence of a generic software best practice of centralised state management emergence across the industry? This table based storage pattern is now common to: - functional frontend apps via redux - classical apps and server backends via relational databases - game engines like the one mentioned here, and Unity's Entity Component System - probably more systems I don't know about It seems to me like separation of state and behaviours is one of those fundamental rules that should apply to most large software applications.