Cache actions on the Kuika platform are used for temporary data storage, fast data access, and performance improvement within the application. With these actions, data can be added to the cache with Push To Cache, retrieved with Fetch From Cache, deleted with Remove From Cache, and checked for existence with Check Key Existence. Cache actions are especially preferred in applications that require dynamic data management, user filters, and temporary form data.

Purpose:

• To improve application performance.
• To manage temporary data quickly and securely.
• To quickly retrieve the user's previous selections or form data.

Advantages

• Can be used in web and mobile applications.
• Provides management capabilities through Redis, Mongo, SQL, and InMemory cache providers.
• Provides the ability to manage and control cache data from a single center.

Cache Action Categories

Push To Cache

• Definition: Stores the value given with a new key in the cache. All values are stored in string format. If executed with an existing key, the previous value is overwritten.
• Important Points: If pushed again with the same key, the previous value is deleted and the new data is saved.

Fetch From Cache

• Definition: Returns the value in the cache with the given key. You can select from a drop-down menu among previously added keys. Newly added values can override existing values.

Remove From Cache

• Description: Deletes the value with the specified key from the cache. If the key is not found in the cache or has been previously deleted, the “Given key does not exist” error is returned.
• Important Points: Data loss may occur if the wrong key is selected.

Check Key Existence

• Description: Checks whether a key defined with Push To Cache exists in the cache. This allows the existence of the key to be verified before performing Fetch From Cache or Remove From Cache operations.
• Important Points: The key must have been created with Push To Cache. If InMemory is selected, the key is lost when the application is closed.