Verified:GitHub

database-architect

Design scalable database architectures with schema modeling, indexing, and migration planning.

Updated May 5, 2026

Search Tags:#indexing #schema design #scalability #microservices #data modeling #migration planning #database architecture

Ready to run

npx skills add https://github.com/Movchanets/Microservices_Learning --skill database-architect-movchanets

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-architect
Source: https://github.com/Movchanets/Microservices_Learning/tree/main/.agents/skills/database-architect
Command: npx skills add https://github.com/Movchanets/Microservices_Learning --skill database-architect-movchanets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design the right database architecture before implementation, so your data layer is scalable, maintainable, and aligned with business needs.

Core Features & Use Cases

Technology Selection: Choose between relational, NoSQL, search, time-series, or hybrid persistence patterns with clear trade-offs.
Schema and Data Modeling: Define entities, relationships, constraints, normalization levels, and physical storage layouts.
Scaling and Resilience Planning: Plan indexing, partitioning, replication, caching, backups, and zero-downtime migration paths.
Use Case: For a microservices marketplace, this Skill can help design separate service databases, event-driven consistency boundaries, and a migration strategy that avoids downtime.

Quick Start

Ask me to design a database architecture for your system, and I will recommend the data model, storage technology, scaling approach, and migration plan.

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 architecture for a new microservices system?▼

Designing scalable database architecture for microservices involves selecting appropriate storage technologies, defining separate service databases, establishing event-driven consistency boundaries, and planning indexing and partitioning strategies.

What is the best way to choose between relational and NoSQL databases for my application?▼

Choosing between relational and NoSQL databases involves evaluating data modeling requirements, consistency needs, and scaling trade-offs to select a storage technology that aligns with your application's specific query patterns and operational demands.

How do I plan a zero-downtime database migration for a multi-tenant platform?▼

Planning a zero-downtime database migration for a multi-tenant platform requires defining a phased migration strategy, establishing data consistency boundaries, and preparing operational readiness checks to transition schemas without service interruption.

When do I need to re-architect my database schema for scalability?▼

You need to re-architect your database schema for scalability when your current data layer struggles with normalization limits, indexing inefficiencies, or partitioning constraints, requiring a shift to a hybrid persistence pattern or new physical storage layout.

How does indexing and partitioning affect database scaling and resilience planning?▼

Indexing and partitioning affect database scaling by optimizing query performance and distributing data loads. They are core components of resilience planning that work alongside replication, caching, and backups to maintain operational readiness.

Can I use this approach to model data for both greenfield systems and existing backends?▼

Yes, you can model data for both greenfield systems and existing backends. The approach applies technology selection, schema modeling, and migration planning to re-architect relational or NoSQL layers and define new physical storage layouts.