An organization has deployed runtime fabric on an eight note cluster with performance profile. An API uses and non persistent object store for maintaining some of its state data. What will be the impact to the stale data if server crashes?
A.
State data is preserved
B.
State data is rolled back to a previously saved version
C.
State data is lost
D.
State data is preserved as long as more than one more is unaffected by the crash
When using a non-persistent object store in MuleSoft, the state data is stored in memory rather than on disk. This means that if a server crashes, all data stored in the non-persistent object store will be lost because it does not survive a server restart or crash. Non-persistent object stores are typically used for temporary data that does not need to be retained across application restarts. Therefore, in an environment where an API is maintaining its state using a non-persistent object store, a server crash will result in the loss of that state data.
References:
MuleSoft Documentation on Object Store
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit