stonebraker-database-architecture

Design database systems using Stonebraker's workload-specific architectural principles.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/copyleftdev/sk1llz --skill stonebraker-database-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stonebraker-database-architecture
Source: https://github.com/copyleftdev/sk1llz/tree/main/domains/databases/stonebraker
Command: npx skills add https://github.com/copyleftdev/sk1llz --skill stonebraker-database-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design robust and efficient database systems by applying the proven principles and architectural patterns of Michael Stonebraker, a pioneer in database technology.

Core Features & Use Cases

  • Workload-Specific Design: Tailor database architectures for OLTP, OLAP, or other specialized workloads.
  • Scalability Principles: Implement shared-nothing architectures for horizontal scaling.
  • Durability Mechanisms: Utilize write-ahead logging (WAL) for data integrity.
  • Extensibility: Design systems with clear extensibility points for custom types and operators.
  • Use Case: When designing a new analytical database, apply Stonebraker's principles for columnar storage and OLAP optimization to ensure high query performance.

Quick Start

Design a new database system following Michael Stonebraker's principles for workload-specific architecture and scalability.

Frequently Asked Questions about stonebraker-database-architecture

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

FAQPage Schema
How do I design a database architecture optimized for specific workloads like OLTP or OLAP?

Database architecture for specific workloads requires workload-specific design principles, separating OLTP and OLAP concerns to optimize storage engines and query processing frameworks for distinct data access patterns.

What is the best way to scale a database horizontally using shared-nothing architecture?

Shared-nothing architecture scales databases horizontally by distributing data across independent nodes, ensuring workload specialization and scalability without resource contention, following principles advocated by Michael Stonebraker.

How does write-ahead logging work for database durability and data integrity?

Write-ahead logging (WAL) ensures database durability by recording transaction changes to a log before applying them to the main storage, guaranteeing data integrity and recovery during system failures.

Can I extend a database system with custom types and operators using these architectural principles?

Yes, database systems designed with clear extensibility points allow developers to integrate custom types and operators, adhering to separation of concerns principles while maintaining query processing framework efficiency.

When should I separate OLTP and OLAP workloads in database design instead of using a unified system?

Separate OLTP and OLAP workloads when designing new database internals to achieve main-memory optimization and high query performance, as specialized architectures outperform unified systems for distinct transactional or analytical demands.