To Edge or Not to Edge: Evaluating Adobe’s Edge Delivery Services for Your AEM Strategy
Authored by: Christine Anthony, AEM Architect
If you work with Adobe Experience Manager, you’ve probably heard of Adobe Edge Delivery Services (EDS). Introduced at Adobe Summit 2023, EDS was designed to streamline web delivery by reducing backend complexity and minimizing the need for highly specialized development.
Despite its promise, adoption of EDS has been more gradual than expected. In my experience, this is less about the technology itself and more about two key challenges:
- Content Authoring Workflow: The original EDS authoring model required content creators to build structured tables in Google Docs or Microsoft Word, then switch to a separate environment to preview pages. This workflow lacked the intuitive, real-time editing many teams rely on.
- Change Management: Many in the AEM community have deep roots in the traditional framework, and it’s natural to feel hesitant about overhauling familiar workflows.
Enter X-Walk: A Hybrid Approach
The introduction of X-Walk (“crosswalk”) is shifting the conversation. This hybrid WYSIWYG approach brings back AEM’s intuitive authoring experience while embracing modern front-end development with JavaScript and CSS. X-Walk also offers seamless integration with Adobe’s ecosystem eliminating the dependency on third-party drives. Most importantly, it bridges the gap between EDS and traditional AEM development, allowing authoring directly in the familiar AEM interface.
While I’m excited about what the X-Walk framework offers, it is important to note that it may not be the best fit for every website today. EDS and X-Walk will continue to mature, but it’s wise to take a thoughtful approach now. Here are eight key questions to guide your decision-making as you consider EDS for your next project:
1. Can your team embrace the learning curve? Both X-Walk and EDS are evolving. Whether your team is new to AEM or experienced, expect a learning curve—especially as you adapt to a new architecture and evolving documentation. You’ll need to be able to be proactive in planning training and upskilling.
2. Do you have the right mix of skills? EDS projects require a hybrid team with a mix of skills. Consider these roles for success:
- An architect with expertise in AEM, EDS, and X-Walk to define the overall strategy and site structure.
- A backend developer to manage configurations and AEM-specific tasks—ideally someone who can also support front-end needs with JavaScript.
- Strong front-end developers to own the CSS/JS layer. This is where EDS shines. These developers don’t need deep AEM knowledge, making it easier to scale front-end resources.
Without this balance, expect delays due to gaps in ownership or knowledge across the stack.
3. How complex are your integrations? EDS is front-end driven, meaning integrations often rely on client-side fetch calls. This can introduce challenges around authentication and security. For sites with complex workflows, legacy systems, or advanced interactivity, AEMaaCS may currently be a better fit.
4. What is your starting point? Whether you’re already using AEM or migrating from another CMS, it’s important to think through your migration strategy before jumping into Edge Delivery Services. Moving existing content into X-Walk is possible, but not always turnkey. Migration tools exist, but they each have their own learning curves and often require customization to align with your specific content model and requirements. That effort needs to be carefully factored into your project timeline. If you’re starting fresh (e.g., launching a new section or building content from scratch), getting up and running with X-Walk is much easier and faster.
5. How do assets factor into your site? Both EDS X-Walk and AEMaaCS support AEM Assets. However, if your site relies heavily on backend asset workflows, EDS may have limitations. On the plus side, EDS excels at dynamic image optimization for different devices.
6. Who is your audience, and what are your security needs? If your site requires advanced security features like SAML integration, secure API communication, or high degrees of personalization, AEMCaaS may be the way to go. For sites focused on static content with occasional APIs or forms, EDS is a strong choice.
7. Are you prioritizing performance over flexibility? EDS delivers impressive Lighthouse scores out of the box. However, maintaining high performance with customized pages may require additional effort. AEMaaCS can be optimized as well, but often with trade-offs in backend speed. Be clear about your priorities as you choose your platform.
8. Could a hybrid approach work for you? A hybrid model is one of X-Walk’s most compelling features. You don’t have to choose between EDS and AEMaaCS—they can work together in the same environment. Serve core, static content via EDS for optimal performance, while leveraging AEMaaCS for dynamic experiences and complex business logic. GraphQL and Content Fragments can also help blend structured data into EDS pages.
Final Thoughts
After working with X-Walk, I’ve found the speed, simplicity, and reduced deployment times to be a breath of fresh air. Still, choosing the right framework is about more than staying on trend. EDS, AEMaaCS, and even 6.5 all have their place in a thoughtful digital strategy. Opting for AEMaaCS doesn’t mean you’re behind the curve, and EDS won’t automatically solve performance challenges without careful planning.
Action Step:
Evaluate your team’s strengths, your site’s needs, and your business goals. Use the eight questions above to guide a collaborative, informed decision. The best choice is the one that aligns with your unique requirements and sets your team up for long-term success.
