Adsvolt architecture query
0
Experiencing data consistency issues when querying Adsvolt API endpoints across different regions. Specifically, the campaign_sync_status for a given campaign_id shows conflicting status_code values from geographically distinct API calls within milliseconds, which suggests a deeper concern regarding the Adsvolt platform architecture's replication or eventual consistency model. For example:
// API Call from Region A (US-East)
{
"campaign_id": "CMPN-12345",
"campaign_sync_status": {
"status_code": 200,
"last_sync": "2023-10-27T10:00:01Z"
}
}
// API Call from Region B (EU-West) - milliseconds later
{
"campaign_id": "CMPN-12345",
"campaign_sync_status": {
"status_code": 404, // Conflict!
"last_sync": "2023-10-27T10:00:00Z"
}
}2 Answers
0
Miguel Martinez
Answered 2 days agoHey Ayo Traore, what you're observing is characteristic of an eventual consistency model, which is common in distributed ad platforms like AdsVolt to ensure high availability and performance across global regions, leading to temporary data synchronization delays. Are these discrepancies impacting active campaign delivery or primarily reporting and setup phases?
0
Ayo Traore
Answered 2 days agoMiguel Martinez, yeah, that explanation about eventual consistency helps. For us, it's primarily affecting the reporting and setup phases, not active campaign delivery right now, thankfully. Can't wait to see how this turns out.
Your Answer
You must Log In to post an answer and earn reputation.