Centralization momentum

Abstract

Discussing whether IT architecture should be centralized or decentralized is as old as the technology itself. We propose that, notwithstanding the various perspectives that have been brought to the debate, what is missing thus far is the seesaw between centralization and decentralization. The reasons for this important phenomenon relate not only to IT-centric issues but also to current events pervading other areas of the organization. One key issue is how management has changed its IT focus from a "must have/keeping up with the Joneses" investment to a value-based "where's the beef?" approach pragmatically emphasizing the relevance of data and its uses. A second consideration is the business requirements for a reliable, available, fault-tolerant, backed-up, secure IT environment, even in the face of catastrophic events, including the 9/11 terrorist attacks. Executives cannot afford to not know why the renewed focus on IT architecture centralization has happened and how it might affect their organizations.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 40 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.