Edge Delievery v/s Sites | Community
Skip to main content
L
learningNeverStops
Level 2
May 20, 2024
Solved

Edge Delievery v/s Sites

  • May 20, 2024
  • 1 reply
  • 767 views

Hello,

 

From various content it seems Edge Delivery's Document-Based authoring is relatively easier for Authors.

It might specially be useful for the customers working with multiple agencies for content creation.

 

What is your take on it?

 

  • Is it easier with little/no training needed?
  • What about Dynamic Content?
  • Is it able to deal with COntent references and flushing them out, when updated?
  • Does it have similar capabilities for MSM (Rollout etc)?
  • What about Workflows, Servlets, Jobs, Event Listeners?
  • How does is work in context of Hybrid Architecture?
  • Can it be used in large organization with multiple functions and complex components?
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by avesh_narang

Adding to this : AEM Sites is a more matured platform with more features, whereas Edge Delivery Services is more recent and focuses on speed and ease of use, Below are the few comparison points  :

FeatureAEM SitesEdge Delivery Services
TrainingDue to its maturity, extensive training resources are availableTraining resources might be limited, as this is newly established
Dynamic ContentSupports dynamic content through components and personalization featuresFocus is on static content , though dynamic content is supported but to limited extent
Content ReferencesEnables referencing of content from other AEM pages or repositoriesContent Fragments can be refrenced but not full AEM pages
WorkflowsOffers robust workflow capabilities for managing content approvals and publishingCurrently lacks built-in workflows, but potential for future integration
Hybrid ArchitectureCan be integrated with other systems and APIs for a hybrid architectureDesigned for a cloud-native, serverless architecture

1 reply

HrishikeshKagne
Community Advisor
HrishikeshKagneCommunity Advisor
Community Advisor
May 20, 2024

Hi @learningneverstops ,

Edge Delivery and Sites in AEM are two different approaches to content delivery and authoring. Here's a comparison of the two:

1. Ease of Use: Edge Delivery's Document-Based authoring is designed to be simpler and more intuitive for authors. It provides a streamlined interface for content creation and editing, making it easier for authors to work with. Sites in AEM, on the other hand, offers a more traditional authoring experience with a full-fledged authoring environment.

2. Training: Edge Delivery's Document-Based authoring requires less training as it focuses on a simplified authoring experience. Authors can quickly get up to speed with the interface and start creating content. Sites in AEM may require more training due to its comprehensive authoring capabilities.

3. Dynamic Content: Both Edge Delivery and Sites in AEM support dynamic content. They provide the ability to create and manage content that can be personalized and targeted to specific audiences.

4. Content References: Edge Delivery and Sites in AEM both handle content references. When content is updated, they ensure that the references are properly flushed and updated to reflect the changes.

5. MSM (Multi-Site Manager): Sites in AEM has built-in capabilities for MSM, including rollouts, live copies, and synchronization of content across multiple sites. Edge Delivery, being a more simplified approach, may not have the same level of MSM capabilities.

6. Workflows, Servlets, Jobs, Event Listeners: Sites in AEM provides a robust framework for implementing workflows, servlets, jobs, and event listeners. These features allow for customizations and automation of various processes. Edge Delivery, being a more streamlined approach, may have limited support for these customizations.

7. Hybrid Architecture: Both Edge Delivery and Sites in AEM can be used in a hybrid architecture, where some content is delivered through the edge network and some content is served directly from the AEM instance. This allows for a flexible and scalable content delivery setup.

8. Large Organizations: Both Edge Delivery and Sites in AEM can be used in large organizations with multiple functions and complex components. However, the choice depends on the specific requirements and preferences of the organization. Edge Delivery may be more suitable for organizations working with multiple agencies and focusing on simplified authoring, while Sites in AEM provides a comprehensive authoring environment for complex content management needs.

Ultimately, the choice between Edge Delivery and Sites in AEM depends on the specific needs and goals of your organization. It's recommended to evaluate both options and consider factors such as authoring experience, customization requirements, scalability, and integration capabilities before making a decision.

Hrishikesh Kagane
    avesh_narang
    avesh_narangAccepted solution
    Level 3
    May 20, 2024

    Adding to this : AEM Sites is a more matured platform with more features, whereas Edge Delivery Services is more recent and focuses on speed and ease of use, Below are the few comparison points  :

    FeatureAEM SitesEdge Delivery Services
    TrainingDue to its maturity, extensive training resources are availableTraining resources might be limited, as this is newly established
    Dynamic ContentSupports dynamic content through components and personalization featuresFocus is on static content , though dynamic content is supported but to limited extent
    Content ReferencesEnables referencing of content from other AEM pages or repositoriesContent Fragments can be refrenced but not full AEM pages
    WorkflowsOffers robust workflow capabilities for managing content approvals and publishingCurrently lacks built-in workflows, but potential for future integration
    Hybrid ArchitectureCan be integrated with other systems and APIs for a hybrid architectureDesigned for a cloud-native, serverless architecture
      Terms & ConditionsAccessibility statement

      Loading footer...