Best Mechanism to flush cache on CDN

Avatar

Avatar
Validate 1
Level 2
rajeevy89244319
Level 2

Likes

10 likes

Total Posts

50 posts

Correct reply

1 solution
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Validate 1
Level 2
rajeevy89244319
Level 2

Likes

10 likes

Total Posts

50 posts

Correct reply

1 solution
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 1
Give Back 5
View profile
rajeevy89244319
Level 2

07-04-2020

Hi All,

 

Could you please confirm which approach is best to clear the CDN cache in multi legged architecture:

1 A - 2P - 2D - 1CDN

 

1. Create CDN flush agent on Author and flush the CDN cache on replication.

2. Create CDN flush agent on one of the publish instance and trigger CDN cache flush from it. 

3. Setup Notify Agent on one of the Dispatchers and then trigger CDN flush using API call from dispatcher.

 

Even though all the above approaches have some limitations, I want to understand what is industry practice and most favored approach on this architecture. If there is any other approach as well, do let me know.

 

Thanks,

Rajeev 

 

 

Thanks,

Rajeev

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 25
MVP
PuzanovsP
MVP

Likes

140 likes

Total Posts

543 posts

Correct reply

165 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Contributor 2
Ignite 10
View profile

Avatar
Validate 25
MVP
PuzanovsP
MVP

Likes

140 likes

Total Posts

543 posts

Correct reply

165 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Contributor 2
Ignite 10
View profile
PuzanovsP
MVP

07-04-2020

Dear Rajeev,

 

The best answer on this I have seen in years is this:

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/can-we-control-the-order-o...

 

"

You cannot control the order in which the replication happens; these run asynchronous and can be blocked/delayed by various reasons (e.g. a publish might be down for restart).

 

If you want to enforce that the Akamai invalidation agent is triggered after the other replication happened, you have to run all activation through a workflow, and use synchronous replication to replicate to the publishs; in the next you can invoke the Akamai invalidation agent. But imagine the case when a publish is down; then your complete replication is blocked!

 

I solve this problem typically by not invalidating Akamai at all, but use TTL-based expiration on Akamai. You will deliver outdated content, but delivering 10 minute old content is typically not a problem.

 

Jörg

"

 

 

Regards,

Peter

Answers (1)

Answers (1)

Avatar

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

106 likes

Total Posts

164 posts

Correct reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

106 likes

Total Posts

164 posts

Correct reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile
sunjot16
Employee

07-04-2020