Understanding the Differences Between AEM and Edge Delivery Services (EDS) Projects
This is a podcast we've wanted to do for a LONG time, and finally had the right people to do it. What are the real differences in mindset, in project makeup, in skillset and in results between a traditional AEM on-prem or AEM Cloud Service project and AEM Edge Delivery Services?
In this episode of the Arbory Digital Experiences podcast, Sean Archibeque, Justin Ranley, and Tad Reeves explore the nuances between AEM and EDS from the viewpoints of developers, operations folk, and project management. We DEFINITELY think you're going to get something out of this podcast.
Also available on Apple Podcasts and as an audio or video podcast on Spotify.
The Document Based CMS: a Dramatic Shift in Mindset
Traditional CMS vs. Edge Delivery
AEM has long been a staple for large brands needing a robust CMS. It serves content dynamically from a centralized repository, which can lead to complexities in setup and maintenance. In contrast, EDS represents a paradigm shift towards a document-centric approach, leveraging content delivery networks (CDNs) to serve static content quickly and efficiently.
Embracing a New Approach
Transitioning from AEM to EDS requires a significant change in how developers and marketers think about content management. Instead of focusing on the CMS as the primary tool for generating and rendering content, EDS encourages users to view content as documents that can be authored and served directly as HTML. This shift can be daunting for those accustomed to the traditional CMS mindset, but it opens up new possibilities for speed and efficiency.
Benefits of Edge Delivery Services
Speed and Efficiency
One of the most compelling advantages of EDS is its speed. Developers can set up environments quickly, often within an hour, allowing them to focus on building rather than troubleshooting complex setups. This rapid deployment capability is a stark contrast to the lengthy processes often associated with AEM, where setting up a new environment could take days.
Simplified Development Process
With EDS, developers can create and test changes in real-time, sharing links to specific branches for immediate feedback. This collaborative approach reduces the time spent on back-and-forth communications and accelerates the development cycle. The ability to quickly iterate on designs and functionalities is a game-changer for teams looking to enhance their digital offerings.
Optimized Performance
Performance is another area where EDS shines. The system is designed to optimize images and content automatically, ensuring that pages load quickly without the need for extensive manual adjustments. This built-in optimization helps maintain high performance even as content complexity increases.
Addressing Concerns and Misconceptions
Complexity vs. Simplicity
While some may view the transition to EDS as complex, the reality is that it simplifies many processes. By focusing on document-based content management, EDS allows teams to streamline their workflows and reduce the overhead associated with traditional CMS setups. This simplicity can be particularly appealing to smaller businesses or those new to digital content management.
Compatibility with Large Enterprises
A common concern is whether EDS can handle the needs of large enterprises. The answer is a resounding yes. EDS is capable of supporting multi-language and multi-region deployments, making it suitable for global brands. Companies like Adobe itself utilize EDS for their own digital presence, demonstrating its scalability and effectiveness.
Conclusion
The transition from AEM to Edge Delivery Services represents a significant shift in how organizations approach content management. By embracing a document-centric mindset and leveraging the speed and efficiency of EDS, businesses can enhance their digital presence and respond more effectively to market demands. As the digital landscape continues to evolve, understanding these differences will be crucial for companies looking to stay ahead of the curve.
Podcast Speakers
Tad Reeves
Principal Architect at Arbory Digital
Tad has been working with Adobe products since 2010 and has extensive experience in website infrastructure. Starting in 1996, he has worn nearly every hat in website delivery from solution architecture to product management, and has over two decades of experience. He loves that Arbory gives him the opportunity to provide honest and effective solutions, even if it means challenging prevailing sales perspectives. When Tad isn’t working, he enjoys mountain biking and exploring nature with his wife & 3 kids.
Justin Ranly
AEM Developer
Justin has sixteen years of experience in the nursing field, with the last ten years dedicated to procedural nursing and radiology. However, he was ready for a new challenge and wanted to become more involved in technology. After applying his skills in a software development bootcamp, he joined the Arbory team. There, he enjoys being surrounded by experts in the field and seeing the direct results of his impact. When Justin isn’t working, he enjoys traveling, attending live shows, and spending time with his family and friends.
Like what you heard? Have questions about what’s right for you? We’d love to talk! Contact Us
More Podcast Episodes You Might Like
The adaptTo() 2024 Conference has just concluded, with an absolutely PACKED 3 days of highly-technical, AEM-centric sessions and discussions. In 3 weeks or so, the recordings of these sessions will be available, but in the meantime we got together with Marta & Michał Cukierman from StreamX to discuss our favorite sessions and what they mean for the AEM community.
How do you solve the constant problem of cache freshness and backend system latency in any modern CMS (especially AEM or Edge Delivery?) In this episode we talk to Michał Cukierman, CTO of Dynamic Solutions and co-founder of StreamX - a digital experience mesh for dramatically and reliably accelerating complicated dynamic content requests from the many constituent systems that make up a modern CMS deployment.
It’s not hyperbole that if you haven’t put considerable effort into rethinking your full site delivery stack in the last few months, you are going to want to. So please - stop reading this right now, pop in some headphones and take this podcast for a walk and consider how it might affect your environment!