1. Home
  2. Docs
  3. Abstract
  4. Methodology
  5. Data vs. Architecture

Data vs. Architecture

As I’m sure you know, our mind, the human mind, contains all of our knowledge. It stores within it everything we know about our external world, our internal world, and everything in between.

But, just like any other data-storage, some of these entities are data, while some are architecture. As some things we know because we learned them, and some we simply know because they are part of the structure that contains the data.

That means that, when looking at relational databases, for example, we have tables, rows, and cells. In those, we can store whatever data we see fit. But, even if there’s no data in the system, there will still be tables, rows, and cells. These don’t exist as a representation of something, but as a way to represent something. These are the primary entities of that specific data storage.

If you were to take your data out of a relational database and move it into a graph DB, for example, then you would lose all the columns, rows, and tables. Instead, the storage architecture will now give you nodes and connections or vertices and edges to work with.

But, what does the architecture gives you when you move data into the human mind, and what do we lose when taking data out of the mind?
Well… that’s what we’re here to try and figure out.