What is the Associative Data Model?

The Associative data model is a model for databases unlike any of those we spoke of in prior articles. Unlike the relational model, which is record based and deals with entities and attributes, this model works with entities that have a discreet independent existence, and their relationships are modeled as associations.

The Associative model was bases on a subject-verb-object syntax with bold parallels in sentences built from English and other languages. Some examples of phrases that are suitable for the Associative model could include:

• Cyan is a Color
• Marc is a Musician
• Musicians play instruments
• Swings are in a park
• A Park is in a City (the bold text indicates the verbs)

By studying the example above it is easy to see that the verb is actually a way of association. The association’s sole purpose is to identify the relationship between the subject and the object.

The Associative database had two structures, there are a set of items and a set of links that are used to connected them together. With the item structure the entries must contain a unique indication, a type, and a name. Entries in the links structure must also have a unique indicator along with indicators for the related source, subject, object, and verb.

How is the Associative Data Model different?

The Associative model structure is efficient with the storage room fore there is no need to put aside existing space for the data that is not yet available. This differs from the relational model structure. With the relational model the minimum of a single null byte is stored for missing data in any given row. Also some relational databases set aside the maximum room for a specified column in each row.

The Associative database creates storage of custom data for each user, or other needs clear cut and economical when considering maintenance or network resources. When different data needs to be stored the Associative model is able to manage the task more effectively then the relational model.

With the Associative model there are entities and associations. The entity is identified as discrete and has an independent existence, where as the association depends on other things. Let’s try to simplify this a little before moving on.

Let’s say the entity is an organization, the associations would be the customer and the employees. It is possible for the entity to have many business roles at the same time, each role would be recorded as an association. When the circumstances change, one or more of the associations may no longer apply, but the entity will continue to endure.

The Associative model is designed to store metadata in the same structures where the data itself is stored. This metadata describes the structure of the database and the how different kinds of data can interconnect. Simple data structures need more to transport a database competent of storing the varying of data that a modernized business requires along with the protection and managements that is important for internet implementation.

The Associative model is built from chapters and the user’s view the content of the database is controlled by their profile. The profile is a list of chapters. When some links between items in the chapters inside as well as outside of a specific profile exist, those links will not be visible to the user.

There is a combination of chapters and profiled that can simplify the making of the database to specific users or ever subject groups. The data that is related to one of the user groups would remain unseen to another, and would be replaced by a different data set.

Next Page: Associative Data Model Disadvantages