edge network batch endpoint vs streaming endpoint | Community
Skip to main content
A
adobegm
Level 2
August 1, 2024
Solved

edge network batch endpoint vs streaming endpoint

  • August 1, 2024
  • 1 reply
  • 1475 views
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 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-api

1 reply

Pradeep_Kumar_Srivastav
Community Advisor
Pradeep_Kumar_SrivastavCommunity AdvisorAccepted solution
Community Advisor
August 1, 2024

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-api

A
adobegmAuthor
Level 2
August 1, 2024

@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
Community Advisor
Pradeep_Kumar_SrivastavCommunity Advisor
Community Advisor
August 1, 2024

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.

Terms & ConditionsAccessibility statement

Loading footer...