Usefulness of Docbase vs. Link compounds

[shee...@gmail.com]

I think I understand the implementation differences between the docbase and link picker compounds, but what is the practical difference and usefulness of each? Is there a reason why I would use docbase over link?

[Woonsan Ko]

Hi,

Here's what I'm thinking of each pros and cons:

[link picker compound]

- stored as child node under document variant node. in hst, you can access those through #getLinkedBean*()

- pros: maybe more natural from model perspective because a link itself exists in its own form, so perhaps there is a good use case in the future with the link node itself?

- cons: when a document contains a lot of compound nodes, it could cause performance issue when reading the document and more memory consumption in internal caching because jcr caching is basically based on caching per node bundle. Having many child nodes means more separate cache items, also resulting in multiple hits on the backend.

[docbase]

- stored as string property. in hst, you can access those through #getBeanByUUID() from each uuid value

- pros: more performant and more lightweight because every compound data is stored in the same document variant node.

- cons: application code should handle the uuid by itself even if hst provided a good utility to convert it to bean, conceptually speaking, not based on model structure.

Regards,

Woonsan

On Fri, May 27, 2016 at 11:27 AM, <shee...@gmail.com> wrote:

I think I understand the implementation differences between the docbase and link picker compounds, but what is the practical difference and usefulness of each? Is there a reason why I would use docbase over link?

--
Hippo Community Group: The place for all discussions and announcements about Hippo CMS (and HST, repository etc. etc.)
 
To post to this group, send email to hippo-c...@googlegroups.com
RSS: https://groups.google.com/group/hippo-community/feed/rss_v2_0_msgs.xml?num=50
---
You received this message because you are subscribed to the Google Groups "Hippo Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hippo-communi...@googlegroups.com.
Visit this group at https://groups.google.com/group/hippo-community.
For more options, visit https://groups.google.com/d/optout.

--

w....@onehippo.com     www.onehippo.com
Boston - 745 Atlantic Ave, 8th Floor, Boston MA 02111
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466