docs.wundaflow.com
  • Overview
  • Roadmap
  • Typical use-cases
  • Glossary
  • Core concepts
    • Workflows
    • Tasks
    • Workers
    • Triggers
    • Signals
    • Webhooks
    • Retry policies
    • Wallets
    • KV Store
  • API
    • API Methods
      • Execute a workflow
      • Pause a workflow
      • Resume a workflow
      • Cancel a workflow
      • Check workflow status
      • Poll for notifications
      • Generate a wallet address
      • Read from KV Store
      • Write to KV Store
    • Authentication
    • Connectors
    • Secrets
    • Errors
  • Token
    • Tokenomics
    • Reward pools
  • Wundaverse
    • Intro
    • Randomness
      • Verifiable Delay Function (VDF)
    • Blobbs NFT
    • WundaGames
      • Wundaflip
  • DISCLAIMER
Powered by GitBook
On this page
  1. Core concepts

KV Store

Having access to a low-latency key-value datastore is highly desirable for many workflow types. Especially so if you plan to build your app entirely on top of Wundaflow and do not maintain any of your own infrastructure.

Our native JavaScript Task has access to two types of KV Store:

Context KV Store (CKV)

This datastore only persists within the context of the current workflow. Data stored within the Context KV Store will therefore not be accessible from any other workflow run.

Global KV Store (GKV)

As the name suggests, this datastore is backed to disk and is accessible from any workflow run in your account. This is useful for storing data associated with contracts/wallets that's too large to keep on the blockchain, or things such as long-running atomic counters.

Additionally, the Global KV Store is also accessible from outside of workflows via API calls. This means that you can read and write data directly from your web2 application for use within your smart contract workflows.

PreviousWalletsNextAPI Methods

Last updated 11 months ago