databases

Design and optimize MongoDB and PostgreSQL schemas for OLTP and OLAP workloads.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/lukebaze/forex-rebate-bot --skill databases-lukebaze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: databases
Source: https://github.com/lukebaze/forex-rebate-bot/tree/main/.opencode/skill/databases
Command: npx skills add https://github.com/lukebaze/forex-rebate-bot --skill databases-lukebaze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pymongo, psycopg2, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides structured guidance for designing, normalizing, and optimizing databases across MongoDB and PostgreSQL, covering OLTP and OLAP use cases to ensure scalable, maintainable data models.

Core Features & Use Cases

  • Database schema design for transactional and analytical workloads across document and relational databases
  • SQL/NoSQL query patterns, indexing, migrations, backups, and performance optimization
  • Best practices, reference navigation, and example patterns to extend or review existing schemas

Quick Start

Design and review a MongoDB or PostgreSQL schema for a new feature, applying the included OLTP/OLAP rules and migration guidelines.

Frequently Asked Questions about databases

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

FAQPage Schema
How do I design and optimize database schemas for transactional and analytical workloads?

Database schema design for transactional and analytical workloads involves applying structured normalization, indexing strategies, and best-practice patterns. This covers OLTP and OLAP contexts to produce scalable, maintainable data models across PostgreSQL and MongoDB.

What is the best way to plan database migrations for PostgreSQL and MongoDB?

Planning database migrations for PostgreSQL and MongoDB requires following structured migration guidelines and best-practice patterns. This ensures consistent schema changes and backward compatibility, minimizing downtime during schema transitions across document and relational databases.

How do I structure indexing strategies for NoSQL and SQL databases?

Structuring indexing strategies for NoSQL and SQL databases requires analyzing specific query patterns and workload types. By applying performance tuning rules, you can optimize both document and relational databases for scalable analytical and transactional data access.

Does this database design approach work for both OLTP and OLAP contexts?

Yes, this database design approach works for both OLTP and OLAP contexts. It provides structured reference libraries and best-practice patterns to normalize and optimize schemas, ensuring scalable models for both transactional and analytical workloads across MongoDB and PostgreSQL.

When should I choose PostgreSQL vs MongoDB for my database schema?

Choosing between PostgreSQL and MongoDB depends on workload requirements: PostgreSQL suits relational OLTP and OLAP contexts needing structured consistency, while MongoDB fits document-based NoSQL workloads. Cross-database integration scenarios can also combine both for specific query patterns.