database-architect

Design scalable database architectures for relational, NoSQL, and time-series systems.

1|1|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/M-Abdullah07/Pharmacy-Billing-App --skill database-architect-m-abdullah07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-architect
Source: https://github.com/M-Abdullah07/Pharmacy-Billing-App/tree/main/.agent/skills/database-architect
Command: npx skills add https://github.com/M-Abdullah07/Pharmacy-Billing-App --skill database-architect-m-abdullah07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing scalable, maintainable data layers and choosing the right database technologies for greenfield or refactor projects.

Core Features & Use Cases

  • Technology evaluation: Assess relational, NoSQL, time-series options and trade-offs for your workload.
  • Schema design & modeling: Conceptual, logical, and physical modeling with normalization and denormalization strategies.
  • Migration planning: Zero-downtime strategies, versioning, and rollback considerations for migrations.
  • Performance-first architecture: Indexing, partitioning, caching, and access pattern optimization across polyglot databases.
  • Use Case: Re-architect a monolithic data store into a multi-model, scalable architecture that supports high-concurrency transactions.

Quick Start

Provide domain requirements and workload patterns, and I will design a scalable data architecture.

Frequently Asked Questions about database-architect

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

FAQPage Schema
How do I design a scalable database schema for a high-concurrency application?

Designing a scalable database schema involves conceptual, logical, and physical data modeling with appropriate normalization or denormalization strategies. It includes indexing, partitioning, and access pattern optimization to support high-concurrency transactions across polyglot databases.

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

Planning a zero-downtime database migration involves defining versioning and rollback considerations for your data layer. The architecture design includes structured migration planning to re-architect monolithic data stores into scalable, multi-model architectures without service interruption.

Can I use a polyglot persistence architecture for time-series and transactional data?

Yes, polyglot persistence architectures support time-series and transactional data by applying performance-first design. This involves technology evaluation and access pattern optimization across multiple database models to ensure maintainability and high concurrency.

When should I re-architect a monolithic data store into a multi-model architecture?

You should re-architect a monolithic data store into a multi-model architecture when facing scalability bottlenecks or needing high-concurrency transaction support. This involves technology evaluation, schema redesign, and performance-first architecture planning to meet evolving workload demands.