database-architect

Design scalable, domain-driven database architectures across relational and NoSQL stores.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/liamtran96/msm-car-booking --skill database-architect-liamtran96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-architect
Source: https://github.com/liamtran96/msm-car-booking/tree/main/.claude/skills/database-architect
Command: npx skills add https://github.com/liamtran96/msm-car-booking --skill database-architect-liamtran96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations struggle to design scalable, domain-driven database architectures that support evolving business needs and microservices boundaries. This Skill provides best practices for data modeling, schema evolution, and technology selection to align data architecture with business domains.

Core Features & Use Cases

  • Proactive domain-aligned data modeling: guidance on domain boundaries, bounded contexts, and entity relationships across services.
  • Scalability planning and migration: strategies for sharding, replication, and migrations with rollback support.
  • Polyglot persistence & technology selection: when to use relational vs document stores, CQRS, and event sourcing patterns.
  • Use Case: For a multi-service fleet booking platform, design a scalable data model that supports bookings, vehicles, users, and locations with event-driven updates.

Quick Start

Ask the skill to review your current domain and propose a scalable, domain-driven data model and migration plan for a new bookings service.

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 data model for a microservices architecture?

Designing scalable data models for microservices requires defining domain boundaries and bounded contexts to align entity relationships across independent services. This Skill guides proactive domain-aligned data modeling to support evolving business needs and distributed service boundaries.

When should I use CQRS and event sourcing in database architecture?

CQRS and event sourcing are needed when building scalable, domain-driven architectures that require event-driven updates and complex state reconstruction. This Skill guides applying these patterns to support polyglot persistence and enterprise-grade system scalability.

How do I choose between relational and NoSQL document stores for my application?

Choosing between relational and NoSQL document stores depends on your domain-driven data modeling needs and scalability constraints. This Skill provides technology selection guidance to determine when to use relational versus document stores for enterprise-grade systems.

What is the best way to plan a database migration with rollback support for a new service?

Planning a database migration with rollback support involves strategies for sharding, replication, and safe schema evolution. This Skill guides scalable migration planning to ensure new services align with domain boundaries without disrupting existing enterprise architecture.

How do I map bounded contexts and entity relationships for a multi-service booking platform?

Mapping bounded contexts for a multi-service platform requires domain-driven design to separate bookings, vehicles, users, and locations into scalable data models. This Skill provides guidance on aligning data architecture with business domains and event-driven updates.