spacetimedb-concepts

Explain SpacetimeDB architecture, reducers, subscriptions, and integration considerations.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/lioartoil/claude-code-handbook --skill spacetimedb-concepts-lioartoil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spacetimedb-concepts
Source: https://github.com/lioartoil/claude-code-handbook/tree/main/skills/spacetimedb-concepts
Command: npx skills add https://github.com/lioartoil/claude-code-handbook --skill spacetimedb-concepts-lioartoil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SpacetimeDB Concepts provides a clear mental model and practical guidance for learning, evaluating, or designing with SpacetimeDB, helping teams understand whether and how to adopt its architecture.

Core Features & Use Cases

  • Architecture overview: Explains the database-as-server model, subscription-driven data flow, and the roles of reducers, identity, and lifecycle hooks.
  • Core Concepts: Defines Table, Reducer, Subscription, Identity, and Module with real-world analogies.
  • Use Case Guidance: Helps you assess fit for real-time apps, collaborative tools, rapid prototyping, and internal tooling.

Quick Start

Review the architecture overview to start learning SpacetimeDB concepts and the Zen of its design.

Frequently Asked Questions about spacetimedb-concepts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the database-as-server architecture in SpacetimeDB?

SpacetimeDB uses a database-as-server model where the database itself acts as the backend server. Clients subscribe directly to database tables, and business logic runs inside the database through reducers, eliminating traditional backend middleware for real-time apps.

How do subscriptions and reducers work in SpacetimeDB?

Subscriptions drive real-time data flow by pushing table updates to subscribed clients automatically. Reducers handle state mutations by executing server-side logic, ensuring subscribed clients receive updates without manual polling or custom event broadcasting.

When should I use a backendless paradigm like SpacetimeDB?

You should adopt a backendless paradigm like SpacetimeDB for building real-time collaborative tools, rapid prototypes, and internal tooling. It fits scenarios requiring synchronized state across clients without maintaining separate backend API infrastructure.

Does SpacetimeDB fit real-time apps and rapid prototyping scenarios?

Yes, SpacetimeDB fits real-time apps and rapid prototyping scenarios well. Its subscription-driven data flow and identity management provide the necessary infrastructure for collaborative tools without building custom backend synchronization logic.

What are the core concepts needed to learn SpacetimeDB?

The core concepts needed to learn SpacetimeDB are Tables for data storage, Reducers for logic, Subscriptions for real-time updates, Identity for user management, and Modules for deployment. These elements define the architecture's data flow and integration model.