Be the first to like this
Even basic AEM deployment involves some network communication. All services need to be aware of each other to make the entire AEM stack usable for both content editors and end users.
The truth is, basic AEM deployments are not that common these days. In many cases it's much more complex - there's plenty of services around you (search engines, caching servers, data feeds, etc) and you need to talk to them in this way or another. Even though that's not the case in your project, most probably you have more than one environment to deal with (unless you're Facebook, as they run just production). All in all it makes perfect sense to run service discovery tool in your AEM infrastructure, as in a long term it gets really painful to manage all these communication channels by hand.
During my talk I'd present how Cognifide combined Consul and Chef to:
- make sure AEM always talk to correct endpoint, no matter how many instances of given service we run
- no longer worry about hardcoded IP addresses in AEM configs or Chef cookbooks
- automatically pick up new services as they go online
- enable even faster, zero-downtime deployments
- orchestrate the entire AEM infrastructure
An interesting fact is that we were able to achieve all of these without a single change in our AEM app!