Expand description
FraiseQL serverless functions runtime.
This crate provides the core infrastructure for executing serverless functions in FraiseQL, with support for multiple runtimes (WASM, Deno, etc.).
§Architecture
FunctionRuntime: Trait for implementing function execution backendsWasmRuntime: WASM component model executor (feature:runtime-wasm)DenoRuntime: JavaScript/TypeScript executor via V8 (feature:runtime-deno)FunctionObserver: Integrates with fraiseql-observers for trigger execution
Re-exports§
pub use host::HostContext;pub use host::NoopHostContext;pub use observer::FunctionObserver;pub use runtime::FunctionRuntime;pub use runtime::SendFunctionRuntime;pub use store::FunctionRecord;pub use store::FunctionStatus;pub use store::FunctionStore;pub use store::memory::InMemoryFunctionStore;pub use triggers::cron::CronScheduler;pub use triggers::cron::CronSchedulerHandle;pub use triggers::cron::CronTrigger;pub use triggers::mutation::AfterMutationTrigger;pub use triggers::mutation::BeforeMutationChain;pub use triggers::mutation::BeforeMutationResult;pub use triggers::mutation::BeforeMutationTrigger;pub use triggers::mutation::EntityEvent;pub use triggers::mutation::EventKind;pub use triggers::mutation::TriggerMatcher;pub use triggers::registry::TriggerRegistry;pub use types::EventPayload;pub use types::FunctionDefinition;pub use types::FunctionModule;pub use types::FunctionResult;pub use types::LogEntry;pub use types::LogLevel;pub use types::ResourceLimits;pub use types::RuntimeType;
Modules§
- host
- Host context trait for function runtime access to FraiseQL services.
- migrations
- Database migrations for functions infrastructure tables.
- observer
- Function observer for executing functions in response to events.
- runtime
- Function runtime trait and implementations.
- store
- Function deployment store for persisting and retrieving compiled function artifacts.
- triggers
- Trigger system for serverless functions.
- types
- Core types for function execution.