fastedge-docs

Open a named store with the static factory KvStore.open("my-store") and call store.get("key"), which synchronously returns an ArrayBuffer or null. KV stores are read-only from app code; provision them in the Gcore portal and populate them via the management API.

530 indicates app initialization failed, 531 is a runtime error from an unhandled exception, 532 means the timeout was exceeded, and 533 signals the memory limit was exceeded. Each has specific debugging strategies documented in the platform error-codes reference.

No. The StarlingMonkey runtime is a strict WinterCG-style environment with no Node.js compatibility layer. node:crypto, node:fs, process, require, WebSocket, and DOM APIs are unavailable; use fetch, streams, and crypto.subtle instead.

Use the fastedge::cache module, a POP-local cache with TTL and atomic counters, since the Web Cache API is not available. Cache.getOrSet provides atomic get-or-populate semantics, and Cache.incr supports rate limiting counters.

FastEdge creates a fresh context instance for each lifecycle hook invocation, and different hooks may run on different servers. Pass data between hooks using set_property and get_property instead of instance fields.

No. Mainstream Node.js SAML libraries depend on xml-crypto's synchronous Node crypto API, which StarlingMonkey lacks. Use WebCrypto-native packages like xmldsigjs, @xmldom/xmldom, and @peculiar/x509 instead.