Skip to content

30_LEVEL_6_TO_8_DEEP_GUIDE.md

Latest commit

 

History

History
99 lines (81 loc) · 3.11 KB

30_LEVEL_6_TO_8_DEEP_GUIDE.md

File metadata and controls

99 lines (81 loc) · 3.11 KB

30 - Levels 6 to 8 Deep Guide (Professional System Builder)

Home: README

Path placeholder: <repo-root> means the folder containing this repository's README.md.

This guide is where you build professional data/integration/dashboard capability.

Objective

Master SQL reliability, monitoring API integration behavior, and browser-first dashboard robustness.

Required docs

Non-negotiable safety rules

  1. Read-only first for source systems.
  2. Stage first, report later (no direct mart writes).
  3. Log run id, source timestamp, batch id, and row counts.
  4. Keep reruns idempotent by design.

Level-6 run pattern (SQL-focused)

cd <repo-root>/projects/level-6/01-sql-connection-simulator
python project.py --input data/sample_input.txt --output data/output_summary.json
pytest -q

Expected output:

... "project": "SQL Connection Simulator" ...
2 passed

Level-7 run pattern (API integration focused)

cd <repo-root>/projects/level-7/01-api-query-adapter
python project.py --input data/sample_input.txt --output data/output_summary.json
pytest -q

Expected output:

... "project": "API Query Adapter" ...
2 passed

Level-8 run pattern (dashboard-resilience focused)

cd <repo-root>/projects/level-8/01-dashboard-kpi-assembler
python project.py --input data/sample_input.txt --output data/output_summary.json
pytest -q

Expected output:

... "project": "Dashboard KPI Assembler" ...
2 passed

Real-environment command template (when you wire real systems)

Use placeholder values first, then replace safely:

# examples only: use safe, read-first credentials and endpoints
export MONITORING_API_URL="https://your-monitoring-api"
export MONITORING_API_KEY="your-api-key"
export DATABASE_URL="sqlite:///data/cache.db"
python your_ingestion_job.py --mode read-only --dry-run

Expected output:

connection successful
records fetched: <n>
dry-run complete (no writes)

Exit gate (must pass before level 9)

  1. You can explain lineage from source to dashboard.
  2. You can recover safely from timeout/auth/schema-drift failure.
  3. You can prove idempotent reruns in your ETL flow.

Primary Sources

Optional Resources

Next

Next: 31_LEVEL_9_TO_10_AND_BEYOND.md →