metodologia-database-architecture

Design database architectures for OLTP, OLAP, HTAP, and mixed workloads.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-database-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metodologia-database-architecture
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/architecture/database-architecture
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill metodologia-database-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Database architecture design and evaluation guidance to help engineers plan, document, and evolve scalable, reliable data systems.

Core Features & Use Cases

  • Schema Design & Modeling
  • Indexing Strategy
  • Partitioning & Sharding
  • Replication & High Availability
  • Migration & Evolution
  • Performance Tuning
  • Security & Compliance
  • Deliverables templates and knowledge graphs

Quick Start

Describe your system context and I will generate a complete database-architecture plan.

Frequently Asked Questions about metodologia-database-architecture

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

FAQPage Schema
How do I design a scalable database schema for mixed workloads?

Database schema design for mixed workloads requires modeling structures that satisfy both OLTP and OLAP needs. You can generate a complete architecture plan covering schema modeling, indexing, and partitioning to meet your specific performance and scalability targets.

What is the best way to plan a database migration without downtime?

Database migration planning requires a structured roadmap to ensure reliability throughout the evolution process. You can generate a detailed migration roadmap template that outlines the necessary steps for evolving your data system while maintaining high availability.

When do I need partitioning and sharding in my database architecture?

Partitioning and sharding are needed in database architecture when your data volume exceeds single-node capacity or write throughput limits. Generating a tailored architecture plan helps identify the exact partitioning strategy required to meet your scalability goals.

How do I create an indexing strategy for high performance database systems?

Indexing strategy for high performance databases involves selecting the right indexes to optimize query execution without sacrificing write speed. You can generate a performance tuning plan template that includes specific indexing recommendations based on your workload type.

Can I use a single database architecture for both OLTP and OLAP workloads?

A single database architecture can support both OLTP and OLAP workloads using HTAP configurations. You can design a mixed workload architecture plan that balances transactional reliability with analytical query performance through targeted replication and tuning strategies.

What should be included in a database performance tuning plan?

A database performance tuning plan should include schema optimizations, indexing strategies, and partitioning configurations tailored to your workload. You can generate a structured performance tuning plan template that satisfies specific reliability and scalability requirements.