Staging
Selects the deterministic market-session close and normalizes the analytical grain to one row per symbol and trade date.
Source truth → analytical truthDevelopment preview — DSEverse is under active development. Market data and AI-generated responses may be delayed, incomplete, or inaccurate. Do not rely on this website for investment decisions.
Analytics Engineering · Read-only observability
A production dbt project turns normalized DSE quotes into session-aware returns, indicators, and reusable marts in ClickHouse—without sitting in the ingestion path.
End-to-end platform
Kafka keeps transport independent. dbt owns deterministic analytical SQL, tests, lineage, and reusable datasets.
Model lineage
Each node has a clear grain and responsibility. Returns and rolling indicators follow observed trading sessions rather than calendar-day joins.
Layered modeling
Selects the deterministic market-session close and normalizes the analytical grain to one row per symbol and trade date.
Source truth → analytical truthCalculates returns and rolling indicators with enough prior-session context to keep incremental and full-refresh results equivalent.
Reusable business logicPublishes stock-day and market-summary datasets for APIs, dashboards, research, and future ML features.
Consumer-ready contractsProduction safeguards
Quality is enforced in the transformation layer while failures remain isolated from ingestion.
Holidays, emergency closures, and special sessions come from the production market calendar.
Recent month partitions are replaced completely so corrected or removed source keys cannot survive.
Incremental models bring prior observed sessions forward before recalculating returns and indicators.
Uniqueness, nullability, price bounds, and current-session freshness are tested on every build.
A nonblocking execution lock prevents concurrent jobs from racing analytical tables or artifacts.
A dbt failure cannot stop scraper, Kafka, normalizer, sink, or raw ClickHouse ingestion.
Execution history
Only aggregate results are public. Run identifiers, commands, resource names, logs, and failure messages remain private.
| Completed | Duration | Models | Tests | Status |
|---|
Loading recent dbt runs…
Public by design
This page reads bounded, sanitized execution summaries from a read-only artifact volume. It cannot invoke dbt, inspect raw logs, query ClickHouse, or mutate the pipeline.