Data Architecture vs Information Architecture: What’s the Difference?

Data architecture

Data architecture defines how data is structured, stored, integrated and managed across an organisation’s systems. It covers data models, databases and platforms, processing pipelines, integration, governance and data quality. Its purpose is reliable, accessible and governed data.

Information architecture

Information architecture organises, structures and presents information so that a person can find and understand it. It belongs to user experience, content management and knowledge organisation: content structures, hierarchies, taxonomies, navigation, metadata and search.

The word information causes confusion in enterprise architecture. In TOGAF, Phase C is called Information Systems Architectures and covers data and applications; it does not deal with information architecture in the user-experience sense.

The differences

The first describes what systems keep and exchange; the second describes what people see and look for.

• Subject: the technical structure of data on one side, the organisation and use of information on the other.
• Perspective: that of systems for the first, that of users for the second.
• Scope: databases, pipelines and platforms; content, knowledge and information structures.
• Goal: govern data across systems; make information easy to find and use.
• People involved: data engineers and IT teams; user-experience, content and knowledge-management specialists.

The customer data example

Data architecture defines the structure of the customer database, its authoritative source and the interfaces that distribute it. Information architecture defines how this information appears in a dashboard or portal, with its labels, its grouping and its navigation.

When one of them is missing

Without data architecture, data fragments, integrations multiply and analyses lose their reliability. Without information architecture, users search for a long time, knowledge stays in silos and decisions rest on incomplete information.

In ArchiLU

ArchiLU describes the data side in the architecture repository: the data objects exchanged, the interfaces carrying them and the applications handling them, with their owners. Each role consults these objects in its own views.