database-design

Design ScalarDB database schemas and transaction models for multi-storage deployments.

6|Updated Feb 18, 2026

Search Tags:#schema #transaction #database-design #design-document #scalardb #multistorage

Ready to run

npx skills add https://github.com/wfukatsu/coding-agent-for-scalardb --skill database-design-wfukatsu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/wfukatsu/coding-agent-for-scalardb/tree/main/skills/database-design
Command: npx skills add https://github.com/wfukatsu/coding-agent-for-scalardb --skill database-design-wfukatsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ScalarDBを前提とした大規模なデータストア設計とトランザクション設計を、対話形式で統合的に行い、実運用に適したスキーマファイルと設計書を自動生成します。

Core Features & Use Cases

スキーマ設計: テーブル定義、キー設計、データ型マッピングを体系化します。
トランザクション設計: 分離レベルとトランザクション境界を定義し、再現性のある処理フローを作成します。
マルチストレージ設計: 複数DBを横断するストレージ配置とマッピングを設計します。
出力生成: schema.json、scalardb.properties、デザイン書を出力します。
実務ケースに適用: マイクロサービスアーキテクチャの要件に基づくネームスペース設計とデータモデルの整合性を保証します。

Quick Start

直感的な対話を通じて、プロジェクト名とサービス一覧を教えてください。

Frequently Asked Questions about database-design

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

FAQPage Schema

How do I design a database schema for ScalarDB microservice architectures?▼

To design a database schema for ScalarDB microservice architectures, you need to define table structures, key strategies, and transaction models. This process generates schema.json, scalardb.properties, and a design document ensuring data model consistency across services.

What is the best way to configure multi-storage transaction models in ScalarDB?▼

The best way to configure multi-storage transaction models in ScalarDB is by defining isolation levels and transaction boundaries across multiple database backends. This approach generates reproducible processing flows and metadata mappings for scalable multi-storage deployments.

How do I generate a schema.json file for a ScalarDB v3.17 deployment?▼

You generate a schema.json file for ScalarDB v3.17 by interactively defining your project name and service list. The process maps data types, plans namespaces, and outputs the schema configuration alongside scalardb.properties and a detailed design document.

Does ScalarDB schema design require defining isolation levels for multiple database backends?▼

Yes, ScalarDB schema design requires defining isolation levels and transaction boundaries to manage multiple database backends effectively. This configuration ensures data consistency and reproducible transaction flows across microservice architectures using multi-storage deployments.

Can I use conversational inputs to plan ScalarDB namespace and data type mappings?▼

Yes, you can use conversational inputs to plan ScalarDB namespace and data type mappings. By providing your project name and service list interactively, the system generates the required schema.json, scalardb.properties, and a comprehensive design document.

When should I not use a multi-storage ScalarDB schema design approach?▼

You should not use a multi-storage ScalarDB schema design approach if your application relies on a single database backend and does not require distributed transactions. This method is specifically built for scalable microservice architectures needing cross-storage transaction consistency.