Edge Delivery Service Architecture Questions | Community
Skip to main content
Level 2
February 15, 2024
Solved

Edge Delivery Service Architecture Questions

  • February 15, 2024
  • 1 reply
  • 1666 views

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
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arunpatidar

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:

 

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 

1 reply

arunpatidar
Community Advisor
Community Advisor
February 15, 2024

Hi,

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

 

Arun Patidar
Level 2
February 15, 2024

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?

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
February 15, 2024

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:

 

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