Whitepaper: Creating the Ideal AEM Deployment Process

AEM Migration

When migrating to a complex platform like Adobe Experience Manager, the engineering team’s focus tends to (understandably) revolve around website functionality. The process and infrastructure required to develop, test and deploy that code over the lifecycle of the site tends to get short shrift.

However, the process your team uses for its migration to AEM can have pervasive and far-reaching effects on your infrastructure layout and budget, as well as your website architecture and how often you can even afford to release code. So, for enterprise architects, developers, DevOps engineers and QA folks involved in an AEM site, we’ve written a whitepaper for you.

It’s called Creating the Perfect AEM/CQ Deployment, and it covers a distilled yet thorough cross-section of what your developers, sysadmins and QA team will need to know to create a successful AEM deployment pipeline.  You can download it for free below.

As an AEM DevOps engineer, I’ve done years of battle in the trenches with website gear, many times spending the majority of my week doing little more than supporting continual “emergency” deployments and their sometimes-disastrous after-effects. I’ve spent years creating and scrapping and recreating countless different deployment processes and pipelines, and from that pain and eventual successes, I’ve written a comprehensive guide which can hopefully be food for thought for you to help your team move toward ideal deployment processes.

Why should you read it? 

As nearly anyone in the business of running a large content-driven site will tell you, there are two ugly truths about code deployment:

  1. The vast majority of website outages will happen soon after a code deployment.
  2. Because of this, code deployment and post-release verification can consume up to 75 percent of your AEM infrastructure engineers’ time.

Presuming the whole idea of saving 75 percent of your engineer’s time and 75 percent of your outages hasn’t yet piqued your interest, here’s another reason to consider reading this little dissertation:

It’s entirely possible — and quite likely — your existing infrastructure architecture and even your planned cloud architecture will entirely block you from having a sane and reliable release process.

This whitepaper covers topics such as:

  • How one would define an ideal code deployment process.
  • The ingredients to create an AEM release process that doesn’t involve sysadmins each time.
  • Aside from AEM itself, what other tools does one need to acquire to have a successful AEM deployment.
  • What metrics (KPIs) are needed to visualize a healthy AEM installation, and where those metrics come from.
  • How to deploy a production AEM installation without incurring downtime.
  • Whether or not it’s recommended (or possible) to apply configurations to running AEM servers.

Please do give the paper a read, as I’d be very interested in any feedback or questions. My team of Rackspace AEM engineers and architects works every day with a vast array of different websites running AEM, all of which have varying requirements, constraints and needs — and a properly architected environment and deployment pipeline can nip such a vast number of problems in the bud before they adversely affect your site and its mission.

To download the whitepaper, fill out the form below. Contact Rackspace with any feedback or questions!

Tad Reeves is an Adobe Experience Manager engineer on the Rackspace Critical Application Support team. He came to Rackspace after working as a DevOps engineer on numerous AEM/CQ-driven websites, as well as having worn a number of other hats around site development, UX design, infrastructure architecture and dreaming of the perfect deployment pipeline. He lives in Portland, Oregon, and spends as much time as possible out mountain biking with his wife and three kids.

3 COMMENTS

LEAVE A REPLY

Please enter your comment!
Please enter your name here