Can someone confirm on the below points:
Solved! Go to Solution.
Views
Replies
Total Likes
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
Hi,
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?
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
Thank you Arun for the information.
Views
Likes
Replies