Architecture of Our Worker

We're going to build a custom worker for Asset Compute service that will produce renditions using the [imgIX][imgix] service.

imgIX is an immensely powerful image processing service, composed of three layers:

The service architecture suggests that it's built primarily to provide a layer delivering transformed and optimized assets directly to a website via the dedicated domain. However, for the sake of this tutorial, we will use it differently - our worker will fetch the rendered images from imgIX and transfer them to AEM storage instead of serving them directly from the imgIX Content Delivery Network on the website.

A conceptual diagram of data flow for our solution looks like this:

Custom worker conceptual architecture