Efficient AwareIM Object Design

[UnionSystems]

It's great how easily you can model real world situations and create multiple relationships between objects in AwareIM but we wonder if too many nested relationships can cause performance problems.

As an example we have a BSV with a "Person" object with a large number of relationship attributes. Many of the objects this object relates to also have relationships to other objects. We've observed when we request an object via the native AwareIM REST service the default result is the entire object with ALL of the objects it relates to and also the related objects relations nested. This can result in a huge XML or JSON data result.

We're curious if when we load that same "Person" object into Context in Aware if a data set is "loaded" of the equivalent huge size of the XML or JSON we observe in REST. If this is the case is it wise to avoid too many levels of nested objects when you are designing your AwareIM data model to reduce Context "Data Volume"??

[aware_support]

Code: Select all

We're curious if when we load that same "Person" object into Context in Aware if a data set is "loaded" of the equivalent huge size of the XML or JSON we observe in REST.

No, it's not equivalent. Aware IM will only load nested references if you access them by rules. Otherwise, it's very well optimised. With JSON and XML Aware IM HAS TO produce the entire tree, but it doesn't have to do it when an object is just loaded into Context.

Code: Select all

If this is the case is it wise to avoid too many levels of nested objects when you are designing your AwareIM data model to reduce Context "Data Volume"??

No, you shouldn't worry about the level of nesting.