Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Edge Delivery Service Architecture Questions

Avatar

Level 2

Can someone confirm on the below points:

  • Which CDN is used by Edge Delivery Service OOTB
  • Role of AEMaaCS -> EDS Content hub uses Azure for Storage and Microservices run on Adobe IO
1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @gagandeepsaluja 
I think EDS for x-walk and franklin is running on same infrastructure thats is AWS. But you can confirm from Adobe.

 

The PIPE is responsible for rendering the content. Running on AWS Lambda, it handles:

• Rendering of full and partial HTML pages.
• Processing JSON from spreadsheets.
• Managing form submissions.
• Handling redirect and OPTIONS requests.

All content that is delivered through the pipeline is stored in the Content Hub on S3:

 

arunpatidar_0-1708015874904.png

Current Architecture 
https://github.com/adobe/helix-home/blob/main/docs/architecture-v5.md

 

The initial architectural was, where bring-your-own (Adobe I/O) runtime framework-driven approach that would allow server-side customisation

https://github.com/adobe/helix-home/blob/main/docs/architecture.md#overview 



Arun Patidar

View solution in original post

4 Replies

Avatar

Community Advisor

Hi,

  • CDN :  Fastly
  • Role of AEMaaCS -> EDS Content hub uses AWS S3 bucket 

arunpatidar_0-1708013297983.png

 



Arun Patidar

Avatar

Level 2

Thank you for the response Arun. Could you also confirm if the Microservices/Pipeline Services to convert the MD -> HTML are also running on AWS or they are on Adobe IO?

Avatar

Correct answer by
Community Advisor

Hi @gagandeepsaluja 
I think EDS for x-walk and franklin is running on same infrastructure thats is AWS. But you can confirm from Adobe.

 

The PIPE is responsible for rendering the content. Running on AWS Lambda, it handles:

• Rendering of full and partial HTML pages.
• Processing JSON from spreadsheets.
• Managing form submissions.
• Handling redirect and OPTIONS requests.

All content that is delivered through the pipeline is stored in the Content Hub on S3:

 

arunpatidar_0-1708015874904.png

Current Architecture 
https://github.com/adobe/helix-home/blob/main/docs/architecture-v5.md

 

The initial architectural was, where bring-your-own (Adobe I/O) runtime framework-driven approach that would allow server-side customisation

https://github.com/adobe/helix-home/blob/main/docs/architecture.md#overview 



Arun Patidar