28-05-2021
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi,
From my point of view this is too complex:
Adobe client console is already using cache for most of the objects that are not changing too oftenly (forms as example) in the same way as a internet browser cache
But what you are requiring is far beyond that point: how do you handle multiple updates on the same objects? It can be updates from your colleagues... Updates from ACC ootb processes (updating the counters of a delivery, broadlogs, etc)... Updates from specific technical workflows (aggregates custom fields on recipients for examples)
unfortunately the best way for that is to enhance network and DB performances:
example perhaps that Adobe Campaign server is hosted in a too far location... If that's the case and that the major part of your users are located in the same place and have the same issue, ask to change the hosted instance on a different location
I know "easy to say hard to put in place"... But unfortunately caching on client side a huge amount of data is hard... And this is also near "impossible" when it comes to a system like Adobe Campaign with a high volume of transactions (insert/update/delete) regarding those data