data-eng-database-architect

Design scalable, secure multi-region data architectures across relational, NoSQL, and time-series stores.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/scanady/nexus-agents --skill data-eng-database-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-eng-database-architect
Source: https://github.com/scanady/nexus-agents/tree/main/skills/data-eng-database-architect
Command: npx skills add https://github.com/scanady/nexus-agents --skill data-eng-database-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently designing scalable, secure data architectures for multi-region deployments, including technology selection, data modeling, and performance strategies to support growth and compliance.

Core Features & Use Cases

  • Design and select appropriate DB technologies (RDBMS, NoSQL, NewSQL) based on requirements, performance, and cost.
  • Model data with robust schemas, indexing strategies, and partitioning plans to enable predictable queries at scale.
  • Plan and validate migrations, replication, HA/DR setups, and security/compliance controls across regions.

Quick Start

Provide a scalable, multi-region database architecture plan for a new project.

Frequently Asked Questions about data-eng-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 multi-region deployments?

Designing a scalable database architecture for multi-region deployments requires selecting appropriate RDBMS, NoSQL, or NewSQL technologies and planning robust data partitioning, replication, and HA/DR setups to ensure predictable queries and compliance across regions.

What is the best way to model schemas and indexing strategies for high scalability?

Modeling schemas and indexing strategies for scalability involves creating robust data models and partitioning plans that enable predictable queries at scale, satisfying specific performance and growth requirements across relational, NoSQL, and time-series stores.

How do I plan a database migration while ensuring high availability and disaster recovery?

Planning a database migration with high availability and disaster recovery involves validating migration steps, replication setups, and HA/DR configurations across regions to maintain operational continuity and satisfy compliance controls.

When do I need time-series stores versus NoSQL for my data architecture?

You need time-series stores versus NoSQL when your data architecture requires specific performance optimizations for time-stamped data, whereas NoSQL handles flexible schemas, both requiring tailored indexing and partitioning plans to scale.

Can I use this approach for greenfield projects and existing database migrations?

Yes, this database architecture approach applies to both greenfield projects and existing migrations, covering technology selection, schema design, indexing strategy, and security compliance across multi-region deployments.