What is the difference between the terms information architecture and database?

Is information architecture and database referring to the same thing? Wh开发者_C百科at are the differences?

You can think of database development (data modeling, etc.) as a subset of information architecture. The former is simply modeling your data persistence for storing your data at rest. The latter, however, can include considerably more. Rich domain modeling, software interaction, documentation, etc. are all "information" being "architected" in an enterprise.

If all your enterprise needs to do is persist data to a database, then the two are roughly the same. But if your business objects interact in more meaningful ways than just relational data schemas, and if there's more information about your enterprise than those schemas, then the information architecture for your enterprise would (should) include much more than just the database.

When somebody says simply 'database' it can refer to:

• a software package (more exactly it's a database engine, or a database server)
• your data

information architecture, OTOH, is the abstract definition that lets you understand what your data means, and how each datum is related to others. It's also what you refer to when developing the software that handles the database. It's like the specs of a program, but for the data.

I found an article here which compares the differences between information architecture and data architecture which is somewhat related to this question as well.