Sling Discovery API
As Adobe moved to cloud-native solution for AEM by introducing AEM as Cloud Service which can be scalable on both Author & Publish instances, there are scenarios for certain use cases which needs to be targeted to be run on one instance rather than all the current running instances. This article talks about how this problem can be solved by using Sling Discovery API. In AEM as Cloud Service, Sling-based deployment consist of several author & publish instances which are scaled depending on the traffic & load. This number of instances would form a cluster that shares a common content repository. The discovery-api bundle is introduced as an abstraction for such scenarios called topology . It provides access to the current topology, allows to be informed of any changes in the topology (Joining & Leaving Instances Nodes). Discovery Entities The following entities are defined by Discovery API. Instance & Instance Description...