Asset Compute microservices extensibility | AEM Community Blog Seeding

Asset Compute microservices extensibility by Adobe

Abstract

AEM as Cloud Service’s Asset Compute microservices support the development and deployment of custom workers that are used to read, and manipulate binary data of assets stored in AEM, most commonly, to create custom asset renditions.

Whereas in AEM 6.x custom AEM Workflow processes were used to read, transform, and write back asset renditions, in AEM as a Cloud Service Asset Compute workers satisfy this need.

This tutorial walks through the creation of a simple Asset Compute worker that creates an asset rendition by cropping the original asset to a circle, and applies configurable contrast and brightness. While the worker itself is basic, this tutorial uses it to explore creating, developing, and deploying a custom Asset Compute worker for use with AEM as a Cloud Service.

Objectives
Provision and set up the necessary accounts and services to build and deploy an Asset Compute worker
Create and configure an Asset Compute project
Develop am Asset Compute worker that generates a custom rendition
Write tests for, and learn how to debug the custom Asset Compute worker
Deploy the Asset Compute worker, and integrate it AEM as a Cloud Service Author service via Processing Profiles
Set up
Learn how to properly prepare for extending Asset Compute workers, and understand what services and accounts must be provisioned and configured, and software installed locally for development.

Account and service provisioning
The following accounts and services require provisioning and access to in order to complete the tutorial, AEM as a Cloud Service Dev environment or Sandbox program, access to Adobe Project Firefly and Microsoft Azure Blob Storage.

Read Full Blog

Asset Compute microservices extensibility

Q&A

Please use this thread to ask the related questions.