||A deployable artifact that contains the AEM product code together with the customer code.
||Cloud-based digital asset processing services that cater to various asset processing use cases, such as rendition generation, PDF processions, subasset handling, text extraction, and so on. See asset microservices overview, for more information.
|Cloud Manager Git Repository
||Where customers store their code and configuration settings.
||AEM as a Cloud Service is running on public cloud infrastructure from multiple vendors behind the scene (such as Microsoft Azure or Amazon Web Services) to deliver the service with the contracted SLA.
|Content Delivery Network (CDN)
||AEM as Cloud Service is shipped with a default CDN. Its main purpose is to reduce latency by delivering cacheable content from the CDN nodes at the edge, near the browser. It is fully managed and configured for optimal performance of AEM applications.
||Where the content is persisted.
||Each instance of the AEM as a Cloud service is isolated from the other instances.
||The AEM publish tier.
||AEM as a Cloud Service uses an orchestration engine to ensure that all author and publish services are scaling as and when needed.