Continuing our series of posts to explain the pieces of AEM Assets, this article covers infrastructure deployment options and other AEM products that are sometimes bundled into an AEM Assets sale.
This information is less focused on interesting DAM capabilities than earlier posts, but it is very important. Infrastructure decisions are harder to change and products have more impacts to price, so be sure you’re making informed decisions on these points.
No, we’re not suggesting that DAM systems are actually including toasting functions.
But if you’ve ever had a sudden panic about leaving the gas on in your kitchen, we’re sorry to be the ones to break it to you that failing to perform routine technical maintenance on your DAM system may have equally explosive results.
Read more about how to avoid exploding your system (and your career).
It’s time for DAM to grow up as a technology system. Out of DAM’s triumvirate of people, policy, and technology, technology is our first thought. But once the software is purchased and implementation completed, most DAM managers turn their focus to people and policy—a never-ending whack-a-mole challenge of governance and compliance.
But benign neglect is not how enterprise technology systems work. Systems age. Applications crash. Storage … gulp … gets corrupted. (While we’re on the subject, how sure are you about your last backup?)
I recently spent a lively couple of hours discussing a DAM issue with a colleague. Freedom’s focus is DAM implementation, and because no two clients (and no two DAMs) are identical, we talk a lot around here. As we each posed questions it became clear we were again, quite literally, speaking different languages.
For those of you who don’t think that “RAID levels” refer to pesticide strength, we offer a handful of technical considerations to keep in mind as you build out DAM functionality within your existing AEM implementation without 404-ing your website.