database

Design scalable databases with data modeling, normalization, and indexing.

24|8|Updated Feb 4, 2026

Search Tags:#design #indexing #database #sql #normalization #nosql #data-modeling

Ready to run

npx skills add https://github.com/Fujigo-Software/f5-framework-claude --skill database-fujigo-software

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database
Source: https://github.com/Fujigo-Software/f5-framework-claude/tree/main/plugins/f5-core/skills/database
Command: npx skills add https://github.com/Fujigo-Software/f5-framework-claude --skill database-fujigo-software

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database design and management challenges are addressed by establishing principled patterns for data modeling, normalization, indexing, and architecture that scale reliably.

Core Features & Use Cases

Understand database types and when to use them (RDBMS, NoSQL, time-series, graph, etc.)
Learn schema design, normalization, denormalization, and indexing strategies for performance.
Use cases across e-commerce, analytics, OLTP/OLAP, and reporting to guide architectural decisions.

Quick Start

Ask for a fundamentals overview of database design and an indexing strategy tailored to your workload.

Frequently Asked Questions about database

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

FAQPage Schema

What is database normalization and when should I denormalize my schema?▼

Database normalization organizes relational data to reduce redundancy, while denormalization merges tables to optimize read performance. Use normalization for OLTP write-heavy workloads and denormalize when read latency in analytics or reporting demands it.

How do I design an indexing strategy for a scalable database?▼

Design an indexing strategy by analyzing query patterns and applying indexing patterns to optimize lookups. Create indexes for frequent filter and join columns to accelerate data retrieval, balancing query speed against write overhead to maintain database performance.

When should I use a NoSQL database versus a relational RDBMS?▼

Choose NoSQL for flexible data modeling, wide-column, or graph workloads requiring horizontal scaling. Use an RDBMS when strict ACID properties and relational schema design are required for reliable transaction processing and complex queries.

How do I model time-series data in a database?▼

Model time-series data by structuring schemas for high-volume sequential writes and appending timestamps. Apply indexing strategies on time ranges to optimize analytical queries and retention policies, ensuring scalable database performance for continuous workloads.

What are the best practices for ACID properties in OLTP and OLAP architectures?▼

Enforce ACID properties by applying schema design patterns that guarantee transactional integrity and consistency. Use normalized structures for OLTP to ensure reliable writes, and denormalized architectures for OLAP to optimize complex analytical reporting.

Does this database design approach work for e-commerce and analytics workloads?▼

Yes, this approach applies principled data modeling across e-commerce and analytics workloads. It guides architectural decisions by mapping OLTP transactional requirements and OLAP reporting needs to appropriate database types, indexing, and schema designs.