edge network batch endpoint vs streaming endpoint

[adobegm]

https://experienceleague.adobe.com/en/docs/experience-platform/edge-network-server-api/overview

https://experienceleague.adobe.com/en/docs/experience-platform/ingestion/tutorials/streaming-record-...

edge network batch endpoint or Non-interactive API vs streaming endpoint.. when to use what end point?

[Pradeep_Kumar_Srivastav]

Hi @adobegm ,

1. Edge Network Batch Endpoint:

• Endpoint: edge.adobedc.net or server.adobedc.net (the Server API supports marking datastreams to accept only authenticated communication via the API, refer to Adobe developer console for this)
• Use Case: Suitable for batch data ingestion (Large infrequent data uploads), allowing large volumes of data to be uploaded in bulk for later processing.

2. Streaming Endpoint:

• Endpoint: Varies (HTTP API etc.) -
  1. Create a Streaming Connection: Set up a streaming connection in AEP using the appropriate connectors (e.g., HTTP API, Kafka, etc.).
  2. Configure Destination: Define the destination where the streamed data will be sent (e.g., another system, data lake, or AEP service).
  3. Obtain Endpoint: Once the connection and destination are configured, you'll receive a unique streaming endpoint URL. This URL will be specific to your AEP environment and the configured connection.
• Use Case: Ideal for real-time data ingestion, enabling instantaneous data collection and processing.

For further details, you can refer to the official Adobe Edge Network Server API documentation
 https://experienceleague.adobe.com/en/docs/platform-learn/tutorials/sources/streaming-ingestion-http...

[adobegm]

@Pradeep_Kumar_Srivastav 

I believe both the APIs (Edge Network Batch Endpoint and Streaming Endpoint) work with authentication (Bearer {TOKEN}). Please correct me if this is wrong.

In a use case where the client can send data to AEP via an endpoint API, is it better to use the Edge Network Batch Endpoint over the Streaming Endpoint? Considering the advantage that the Edge audience can be evaluated in real-time over the Streaming audience?

If cost is not a factor and the client expects improved latency, quick audience evaluation, and activation to destinations or utilization in AJO for real-time communications, which is a better API option to choose to send data to AEP?

[Pradeep_Kumar_Srivastav]

In your case where the client looking to send data to Adobe Experience Platform (AEP) with a focus on improved latency, quick audience evaluation, and real-time activation to destinations or utilization in Adobe Journey Optimizer (AJO), the Edge Network Streaming Endpoint is generally the better option over the Edge Network Batch Endpoint as Streaming data directly into the Edge Network ensures lower latency compared to batch processing.

Hope this helps.

[adobegm]

@Pradeep_Kumar_Srivastav 

Is the Edge Network Streaming Endpoint nothing but an interactive endpoint? If so, I believe it supports communication only with Adobe Experience Platform and Adobe Experience Cloud services. Does the interactive endpoint allow sending data from applications outside Adobe Experience Cloud services? If not supported, in a scenario where data is coming from an application that is not part of Adobe Experience Cloud services, which API option (Edge Network Batch Endpoint, HTTP API) is better for sending data to AEP?

If data comes via the Edge Network Batch Endpoint, would it be eligible for edge segmentation?

The client has middleware in the architecture, so any request payload can be converted into an AEP-understandable XDM format to call AEP REST API endpoints (Edge Network Batch Endpoint, HTTP API).

It would be great to see the use cases for when to use each API (interactive, Edge Network Batch Endpoint, HTTP API).