Developing Apama Applications > Developing Apama Applications in EPL > Using Correlator Persistence > When non-persistent monitors are useful
When non-persistent monitors are useful
A correlator that is running with persistence enabled can have persistent and non-persistent monitors injected. Non-persistence is a good choice for a monitor that does one or more of the following:
*Uses legacy code that does not use the persistence feature. See Designing applications for persistence-enabled correlators.
*Interacts with user-defined correlator plug-ins or Apama correlator plug-ins other than the Time Format or MemoryStore plug-ins.
*Contains large amounts of fast-changing state that is undesirable to persist for performance reasons.
*Operates as a stateless utility that just responds to incoming events.
*Contains minimal state that can be reconstructed by the onBeginRecovery() action on a persistent monitor.
Also, all JMon monitors are non-persistent monitors.
Copyright © Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or its Subsidiaries and or/its Affiliates and/or their licensors.
Use, reproduction, transfer, publication or disclosure is prohibited except as specifically provided for in your License Agreement with Software AG.