Panel Discussion: AEM Headless
Join our panel discussion around AEM Headless in its various scenarios. Bring your own questions to the table.
What are the SEO and Google indexing implications of a Headless Client Side Rendered SPA Application? There are lots of conflicting informations out there. Is indexing e.g. by Google working fine? Or do you always need SSR for good SEO and indexing?
Is there any best practices to make DoS attacks against GraphQL endpoints harder?
Are you thinking of getting rid of the POST-requests for the saved queries? As they are difficult to cache and pose extra load on your AEM instances.
Why content fragment does not allow all or many standard dialog components and techniques. For example multifield wrapped around any combination of children (more than one) Also, Not able to include snippets like we do in normal dialog
How would you recommend to keep control of versioning of content / content structures etc if your content is consumed by many different applications? Especially when content gets restructured / moved / ...
What's the recommendation for smart cache invalidation? Publishing of fragments does not invalidate the associated caches automatically (persisted queries).
It doesn’t indeed, but the persisted queries can provide Cache-Control headers. Like anything in AEMaaCS, you will end up setting a TTL that configures the caching behaviour.
Caching GraphQL is possible if the proxy/CDN understands the protocol and is able to construct a cache key, even for POST. Akamai for instance has added support for such caching. Will Adobe put in work to enable it in Dispatcher or in the "Adobe CDN" offered?
With content fragments you can "only" model domain objects like products, blopost etc. But how do you add a page to navigation to e.g legal/faq pages to make a spa website
Question for Adobe: Are there any plans to extend the graphQL api with a business logic layer to have more control on the data delivered?
This can be achieved with https://developer.adobe.com/graphql-mesh-gateway/
You can also implement this directly in Sling/AEM via custom GraphQL data fetchers.
Considering the conferences talks until now, one gets the impression that Adobe is distancing itself from AEM and Sling. Does classic AEM still have a future, or is it becoming just another content storage among many?
Any plans on releasing the new Content Fragment editor for AEM on-premise?
Is "everything is content" dead?
Mostly because of the power the tool gives you and the potential changes you could make that would break your applications.