信息架构和数据库这两个术语有什么区别？
信息架构和数据库指的是同一个东西吗？有什么区别？
Is information architecture and database referring to the same thing? What are the differences?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
当有人简单地说“数据库”时，它可以指：
信息架构 OTOH 是一个抽象定义，可让您了解数据的含义以及如何使用每个数据都与其他数据相关。这也是您在开发处理数据库的软件时所指的内容。这就像程序的规格，但针对的是数据。
When somebody says simply 'database' it can refer to:
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.
您可以将数据库开发（数据建模等）视为信息架构的子集。前者只是对数据持久性进行建模，以静态存储数据。然而，后者可以包含更多内容。丰富的领域建模、软件交互、文档等都是企业中正在“架构”的“信息”。
如果您的企业需要做的只是将数据保存到数据库，那么两者大致相同。但是，如果您的业务对象以比关系数据模式更有意义的方式进行交互，并且有关您的企业的信息比这些模式更多，那么您企业的信息架构将（应该）包含的不仅仅是数据库。
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.