Expand my Community achievements bar.

Join us in celebrating the outstanding achievement of our AEM Community Member of the Year!

Acceptable Scheduler Frequency in AEMaaCS

Avatar

Level 2

Hi,

 

We're integrating with an external system using a scheduler to make API calls and sync data to AEM under /var/abc/... The client requests a synchronization frequency of 30-60 minutes for approximately 100 nodes within AEMaaCS.

 

Is that acceptable or what are all the factors we need to consider if we are going with shortened frequency?

 

Note: Due to security reasons we cannot go with Client-Side or On-demand calls.

3 Replies

Avatar

Community Advisor

Hi @srikrishnank190 

 

I think 30-60 minutes frequency for updating approximately 100 nodes within AEMaaCS will be fine.

 



Arun Patidar

Avatar

Level 8

Hi @srikrishnank190 

 

I believe this kind of decision depends on some factors:
- Is that a flat 100 nodes structure or a deep nested structure ?

- Are the nodes having lots of properties holding big data or not ?

- How much time an average import process takes for the expected data to be fetched and written in those 100 nodes ?

- How often does the external system accepts requests without throwing HTTP 429 status ?

- How critical is the imported data to be always as fresh as possible for the end user ?

 

All these questions should help you calibrate the import period. I also think that usually on average 100 nodes is a small amount of data, and AEM should support a much frequent import period then 30-60 minutes. But if business requirement is for that, I would go with that at the beginning, and leave some room for improvement later if necessary.

Avatar

Level 4

Syncing data every 30-60 minutes with 100 nodes is acceptable, but consider these factors:

  1. AEM Load: Frequent syncs can strain resources (CPU, memory).
  2. Cache Invalidation: Ensure cache settings are optimized for frequent updates.
  3. API Rate Limits: Check AEMaaCS API rate limits to avoid throttling.
  4. Data Volume: Ensure sync size doesn't overwhelm AEM processing.
  5. Error Handling: Implement retries, logging, and monitoring for failures.
  6. Security: Follow secure API call practices.

Make sure your infrastructure can handle the frequency and load.