I need to understand the role of Adobe I/O in AEMaaCS.
1. Say, if AEM author/publisher wants to connect to an external API, should we need to always go through Adobe I/O (Calling Runtime action as mentioned here) or shall we make a call directly from AEM author to External API.
2. Say if the same external API call need to be sent from client side(from front end code), then also same question arises. Should we connect through I/O Runtime or direct call to external api.
Adobe I/O is a cloud-based gateway to integrate with Adobe API’s, SDK’s and server-less environment that enables developers to easily integrate, extend and customize Adobe’s cloud services. Adobe I/O is adding more APIs to the Adobe I/O Console’s already rich offering, including:
Adobe Cloud Platform Data Service
Adobe Sensei Content AI Services
Launch, by Adobe
Adobe I/O Events allows developers to create event-driven applications via webhooks or functions, using the workflow they want, including third-party apps and services. We will be able to programatically deliver event-based experiences using:
Adobe Experience Manager
Adobe Analytics Triggers
Creative Cloud Assets
To answer your question:
1. If you want to connect to any External API, let's say anykind of REST API or SOAP API, it can directly go from your instance.
2. If you want to make any client side call, it is preferred to make call from AEM using the API based event than calling it directly from client side.