operational-vs-analytical-splitter

What problem does it solve?

This Skill helps you decide which workloads should stay on the transactional database and which should move elsewhere when reporting, dashboards, exports, or analytics are slowing production.

Core Features & Use Cases

• Workload classification: Separates OLTP, OLAP, and hybrid workloads so you can see which queries belong on the primary and which do not.
• Mechanism selection: Recommends the cheapest adequate offload path, such as read replicas, CDC into an analytical store, materialized views, or cache, based on freshness tolerance.
• Boundary and cutover planning: Produces a split boundary, a stop-doing list for the primary, and a staged cutover with dual-run validation and consumer sign-off.
• Escalation and handoff guidance: Redirects destination design to the warehouse architect, CDC transport to the streaming architect, and cache design to the caching specialist.
• Use Case: A morning dashboard refresh is spiking checkout latency, so you use this Skill to identify the offending workload, assign an offload mechanism, and prevent the dashboard from returning to the primary later.

Quick Start

Analyze our transactional database workloads, classify what should stay or move, and give me the split boundary, freshness assumptions, mechanism choice, and cutover plan.