Data That Need to Be Shared and Current Should Be Centralized

Transactional data that are high volume and shared across locations should be centralized. Additionally, if the data for all locations must be current, centralization becomes mandatory. Some organizations have tried to work around this by replicating updates to distributed databases in remote locations with limited success. Using a replication approach increases the complexity of an organization's data architecture and results in increased network traffic.

If any of the following criteria are present within your organization, a centralized database strategy is mandatory:

  • More than a handful of users requiring access to up-to-date data. Usually this may include access to OLTP systems.

  • A handful of users and no distributed locations. Sometimes an organization adopts the departmental mind-set, but this should be avoided.

  • Multiple locations but a lack of appropriate skill sets and/or tools to manage distributed data.

  • A business requirement to provide consolidated data for federated metadata on an open platform.



Practical Guide to Enterprise Architecture, A
A Practical Guide to Enterprise Architecture
ISBN: 0131412752
EAN: 2147483647
Year: 2005
Pages: 148

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net