World of Warcraft analytics built for performance, patch intelligence, and economy players.
This first build establishes the product shell for WOWanalytics.al1e.dev around the documented MVP: spec performance dashboards, patch meta tracking, a basic profit calculator, and realm price views.
Target latency
< 500ms
Frontend requests are intended to stay fast by reading from aggregated tables and Redis-backed caches.
Daily users
50k+
The design assumes a public-facing analytics site with broad access for guests and deeper features for registered users later.
Data volume
100M+
Auction data is expected to dominate storage, which is why partitioning and background processors are central to the architecture.
MVP scope
4 modules
The initial release is tightly scoped around spec analytics, patch tracking, basic profit calculation, and realm price views.
Performance
Spec dashboard
Summaries and deep dives for class and spec performance across raids and Mythic+.
- •Average, median, and top-percentile DPS
- •Representation and success-rate views
- •Dungeon and raid-boss breakdowns
Meta
Patch tracker
A patch comparison surface that shows how the meta shifts over time.
- •Representation and DPS movement
- •Patch-to-patch comparisons
- •Automated shift alerts and highlights
Economy
Profit calculator
Realm-aware market tools for evaluating crafting and resell value.
- •Material cost versus sell price
- •Margin and expected profit output
- •Realm and region preference persistence
Discovery
Realm price viewer
Fast item and market views powered by auction aggregation tables instead of raw listings.
- •Price history windows
- •Volume and volatility summaries
- •Base for later flip-finder expansion
Pipeline-first design
System architecture
External APIs
Blizzard, Warcraft Logs, and Raider.IO feed the platform through scheduled ingestion workers.
Raw data storage
Large append-heavy tables preserve source records for auditing, replay, and reprocessing.
Processing workers
Background jobs compute spec summaries, patch changes, item market statistics, and profit snapshots.
Frontend API
The website is intended to query only precomputed tables and cached views for predictable response times.
First implementation pass
Build priorities
Establish product shell
Phase 1Create the visual identity, page architecture, and navigation that maps directly to the design document.
Model core data contracts
Phase 2Translate documented metrics and filters into typed frontend interfaces and backend-ready API contracts.
Wire live data
Phase 3Connect the frontend to the future API layer for spec summaries, patch deltas, and market snapshots.