moai-domain-database

Design and optimize multi-database architectures across PostgreSQL, MongoDB, and Redis.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tjdwls101010/seongjin_extension_youtube-summarize --skill moai-domain-database-tjdwls101010
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-domain-database
Source: https://github.com/tjdwls101010/seongjin_extension_youtube-summarize/tree/main/.claude/skills/moai-domain-database
Command: npx skills add https://github.com/tjdwls101010/seongjin_extension_youtube-summarize --skill moai-domain-database-tjdwls101010

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database Domain Specialist - Provides patterns and implementations for PostgreSQL, MongoDB, Redis, and multi-database data strategies to build scalable, maintainable data architectures.

Core Features & Use Cases

  • PostgreSQL: Advanced relational patterns, optimization, and scaling
  • MongoDB: Document modeling, aggregation, and NoSQL performance tuning
  • Redis: In-memory caching, real-time analytics, and distributed systems
  • Multi-Database: Hybrid architectures and data integration patterns
  • Performance: Query optimization, indexing strategies, and scaling
  • Operations: Connection management, migrations, and monitoring

Quick Start

Initialize a multi-database stack with a unified interface and run sample queries:

  • Setup PostgreSQL, MongoDB, and Redis using a DatabaseManager
  • Perform a sample user_data retrieval and analytics query

Frequently Asked Questions about moai-domain-database

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

FAQPage Schema
How do I design a multi-database architecture across PostgreSQL, MongoDB, and Redis?

Multi-database architecture combines relational (PostgreSQL), document (MongoDB), and in-memory (Redis) stores in a single system. Design involves selecting the right database for each data type, establishing cross-database routing logic, managing connections, and synchronizing data across stores to optimize for scalability and query performance.

What indexing and query optimization strategies work across PostgreSQL and MongoDB?

Query optimization differs between PostgreSQL's relational indexes and MongoDB's document indexing. Strategies include identifying hot queries, building composite indexes, analyzing execution plans, denormalizing selectively in MongoDB, and leveraging aggregation pipelines to reduce data transfer and improve response times across both systems.

How do I handle caching and real-time analytics with Redis in a polyglot database stack?

Redis provides in-memory caching and real-time analytics in polyglot stacks by storing frequently accessed data, materialized aggregations, and session state. Configure Redis alongside PostgreSQL and MongoDB to reduce query load, enable fast data retrieval, and support real-time dashboards without overwhelming primary databases.

What patterns prevent data inconsistency when migrating or syncing across multiple databases?

Data synchronization across PostgreSQL, MongoDB, and Redis requires consistent write ordering, transaction boundaries, change data capture, and idempotent operations. Implement unified operations through a manager layer, monitor replication lag, version schemas, and test rollback scenarios to maintain integrity during migrations and ongoing sync.

Can I use connection pooling and monitoring for PostgreSQL, MongoDB, and Redis simultaneously?

Connection pooling and monitoring work across all three databases through a centralized DatabaseManager that routes connections, tracks pool saturation, logs query latency, and alerts on failures. This unified approach prevents connection exhaustion, identifies bottlenecks, and ensures reliable operations across your entire multi-database stack.

When should I partition or shard data across PostgreSQL and MongoDB instead of scaling vertically?

Partition when single-node throughput hits limits, data exceeds available memory, or query latency becomes unacceptable. PostgreSQL supports declarative partitioning by range or hash; MongoDB uses shard keys. Partitioning distributes load, enables parallel queries, and supports horizontal scaling for high-volume applications, but adds operational complexity.