Sing Models - an ongoing debate | AEM Community Blog Seeding

[kautuk_sahni]

Sing Models - an ongoing debate by Divanshu Goyal

Abstract

Sling models are been there for long years when we talk about Adobe Experience Manager, but undoubtedly it had always been the developer's dilemma.

Whether to use them all the time or it should be utilized only for utmost need?

We always talk around the model while accessing values from JCR and we always have our opinion that when we can directly use ${properties. title} to access it. Why use the sling model for that? Even for the simple component, is it not an overhead? Can't we use HTL to express the logical implementation for the component rendering?

To answer these questions following points you may agree with,

It's been a time since everyone now knows the coined term "content-as-a-service" which means exposing the content as a JSON so that anything that is built on top of the CMS can consume the content without exposing any separate endpoint. Taking this point into consideration if we don't have a sling model, we may end up having some components partially showing some attributes as part of JSON and some not showing anything at all while it's an OOTB AEM feature which may not lead to great client delivery.

Read Full Blog

Sing Models - an ongoing debate

Q&A

Please use this thread to ask the related questions.