What is the most performant out-of-the-box solution in Anypoint Platform to track transaction state in an asynchronously executing long-running process implemented as a Mule application deployed to multiple CloudHub workers?
What is the most performant out-of-the-box solution in Anypoint Platform to track transaction state in an asynchronously executing long-running process implemented as a Mule application deployed to multiple CloudHub workers?
In the context of Anypoint Platform, the most suitable out-of-the-box solution to track transaction state in an asynchronously executing long-running process across multiple CloudHub workers is the Persistent Object Store. This storage mechanism is designed to persist data, making it accessible across different instances of the Mule application, ensuring consistency and reliability in tracking the state of transactions. Other options, such as Redis distributed cache, java.util.WeakHashMap, and File-based storage, either require additional setup or are not suitable for the CloudHub environment.
Persistent Object Store
C. Persistent Object Store
Correct answer: C
Answer: C
C. Persistent Object Store
A. Redis distributed cache (Not an answer cause Redis is not out of box) B. java.util.WeakHashMap, Cannot imagine how this will work. C. Persistent Object Store . This is the only option that will work. D. File-based storage (Wont work because they are cloudhub workers)
Answer: C