Expand my Community achievements bar.

SOLVED

How to fix GET call timing out

Avatar

Employee

Hi experts,

we have a get api which fetches a large amount of data in sort of a DFS fashion.

Like this A- is linked with B, B is linked with C, 

then it should get all A,B,C along with all the labels of all A,B,C and the version history of each of the files.

Then we build our UI upon this to should a is linked with b and C and in in the drop down any version can be selected and the corresponding file.

this works for a small sets of links, but when we have a very large set with loads of version history the ui often times out saying that the GET call failed but the call returns data in like 15-20 min.

In cloud it times out in 60 sec. 

Can you please help us as to how to change this design. so that the call does not time out.   we start crawling from the seed file so any help would be great. we do cache the data once called.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Few factors to consider:

- How frequently do you need to fetch this information from external system?

- If it does not need to be real time, consider pulling information regularly and caching it

- The content can also be extracted and kept in a format, that can be used by AEM Servlet/Sling Model to efficiently return the results.

- Consider caching on dispatcher and CDN level

 

Use caching and pre-processing to your advantage and reduce the UI processing for each request


Aanchal Sikka

View solution in original post

2 Replies

Avatar

Community Advisor

Could the server you are calling for data be rate-limiting your requests based on ip or user account?

 

Avatar

Correct answer by
Community Advisor

Few factors to consider:

- How frequently do you need to fetch this information from external system?

- If it does not need to be real time, consider pulling information regularly and caching it

- The content can also be extracted and kept in a format, that can be used by AEM Servlet/Sling Model to efficiently return the results.

- Consider caching on dispatcher and CDN level

 

Use caching and pre-processing to your advantage and reduce the UI processing for each request


Aanchal Sikka