Content as a service vs Sling Model Exporters vs others for exposing JSON from AEM | Community
Skip to main content
S
sandeepk7656774
Level 4
October 20, 2017

Content as a service vs Sling Model Exporters vs others for exposing JSON from AEM

  • October 20, 2017
  • 1 reply
  • 3623 views

Hi All,

There can be many ways to expose content from AEM as JSON

  1. Manipulate/filter infinity.json to provide required JSON
  2. Write a custom servlet, which reads JCR and exposes required JSON
  3. Content as a service - new feature being provided in AEM 6.3. There doesn't seems to b much official (Develop/Administer/Author) documentation on this. Is there a role of Content Fragments and Experience Fragments (not sure of difference between 2 yet)
  4. Sling Model Exporters - Provided by Sling.
  5. Any other?

Has anyone evaluated different options? What is the difference between CaaS and Sling Model Exporters? If there are some reference links which help us understand and evaluate different options please share experiences.

Thanks

Sandeep

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    1 reply

    smacdonald2008
    smacdonald2008
    Level 10
    October 23, 2017

    There is quite a bit of information on Sling Models in that link.

    If you want complete control over which nodes are exposed - you can write a custom service using JCR API and then convert the result set to JSON. This would be manual coding.

    S
    sandeepk7656774Author
    Level 4
    October 25, 2017

    Seems like the Caas feature is overridden by Sling Model Exporter. Below is the quote from reference link

    Adobe is probably trying to reuse feature provided by Sling instead of reinventing the wheel, also focusing on providing headless capabilities to cater to different channels/type of apps. I guess the future would be headless capabilities to support SPA etc.

      Terms & ConditionsAccessibility statement

      Loading footer...