Blogs > What is Edge Delivery Service
AEM EDS
Introduction to Edge Delivery Services
| December 1, 2024Happy to find you here. Welcome to another learning.
What is Edge Delivery Services
Edge delivery service is a part of AEM as a cloud service It is an individual module/functionality in AEM as a cloud service and not dependent on AEM You can Build, Run and Author a website using Edge Delivery service without AEM It can be integrated with AEM author to create content/site authoring however, AEM authoring is not mandatory for content authoring It supports two way of authoring one is document-based authoring and another one is WYSIWYG(What You See Is What you Get) authoring.
Edge Delivery Service Architecture
Franklin /Edge Delivery Service is based on a serverless micro-services architecture.
Each individual service is designed to be single-purpose. The connections between the different services make up the overall architecture.
All inter-service communication is based on HTTPS.
It is a composable set of services that enables a rapid development environment.
The architecture is typically composed of three layers.
Authoring Layer:
In this we create content for edge delivery service, we have following ways to create content
AEM authoring using universal editor
We can create content using google docs or Microsoft docs or spreadsheet with teams and slack you can take help of adobe and build channels to ask for the help as it is a new product.
your code and configuration always stay in GitHub and that code is moved to edge delivery services when needed.
Edge Delivery Layer:
It is micro service based serverless infrastructure build on cloud.
Client infrastructure:
This is also the CDN layer from client side on top of Edge Delivery Service CDN
The entire edge delivery service is implemented in two ways:
After all the develeopement the storage and processing is done with the below mentioned servers
AWS
In AWS there are three components AWS-S3, Lambda and Fastly
AWS s3 is used for storage or content hub
Lambda is used for processing and computing
Fastly is used as CDN for this stack
CloudFlare
In CloudFlare there are three components R2, Worker and Cloudflare-CDN
R2 is used for the storage.
Worker is used for the computing.
CloudFlare-CDN is used for the CDN
There are bascially following 4 main parts involved in Edge Delivery Service(EDS):
I will explain each and every part in detail
Edge
Edge is basically the CDN part it involves three types of CDN
Bring your own cdn(BYOCDN)- this is basically the CDN that client can include above the EDS CDN.
Outer CDN- In EDS we have two url one is live url and one is preview url outer cdn will display you the live url content which is published.
Inner CDN- Thi will basically shows you the preview of the content you have authored.
PIPE(Pipeline)
The main delivery functionality is provided PIPE (Pipeline) and main pipeline is helix-plpeline-service, which uses the helix-html-pipeline framework to render HTML and renders filtered JSON directly after applying some filters. The Pipeline Service pulls configuration from the Code Bus and the published Content from the Content Bus The pipeline service runs as an AWS Lambda function.Mainly the pipeline is used to convert the content autored in documents to hypermedia
Authoring/Author
Authoring can be done using the google docs or microsoft docs and can be stores in google drive or share point and can be published from there.
Authoring mainly involves 3 things
Authoring- it can be done using google docs or microsoft docs or any third party document service.
SideKick- It is very important it is an extension which is used to publish, unpublish or delete the content from th website
Dev
Developement part is mainly done in the github repo that we will create in this we need to install AEM code sync github app which is know as franklin bot and the content is served from the documents stores in google drive or sharepoint
