Proyek: Analisis & Visualisasi Data Lalu Lintas (Go)Proyek: Analisis & Visualisasi Data Lalu Lintas (Go)
📚 Level 2 · DeveloperLevel 2 · Developer🌏 Dual Bahasa (ID / EN)⚡ VibeKoding Native
Modul praktis Level 2 VibeKoding: Proyek: Analisis & Visualisasi Data Lalu Lintas (Go).Modul praktis Level 2 VibeKoding: Proyek: Analisis & Visualisasi Data Lalu Lintas (Go).
OverviewOverview
This project requires you to build a traffic data analysis platform using Go, based on a real PRD. Unlike previous CRUD systems, you'll build a complete data pipeline: "data ingestion → aggregation → alerting → visualization." This type of data product is very common in IoT, monitoring, and operations analytics.This project requires you to build a traffic data analysis platform using Go, based on a real PRD. Unlike previous CRUD systems, you'll build a complete data pipeline: "data ingestion → aggregation → alerting → visualization." This type of data product is very common in IoT, monitoring, and operations analytics.
This is the comprehensive practical section of Stage 2, and your first encounter with Go. Don't worry — with your JavaScript/TypeScript background, learning Go isn't difficult. The focus is on understanding data pipeline design principles.This is the comprehensive practical section of Stage 2, and your first encounter with Go. Don't worry — with your JavaScript/TypeScript background, learning Go isn't difficult. The focus is on understanding data pipeline design principles.
PrerequisitesPrerequisites
Before starting this project, you should already be familiar with:Before starting this project, you should already be familiar with:
Backend API design and development ([API Code](../../backend/ai-interface-code/))Backend API design and development ([API Code](../../backend/ai-interface-code/))
Database fundamentals and Supabase ([Database to Supabase](../../backend/database-supabase/))Database fundamentals and Supabase ([Database to Supabase](../../backend/database-supabase/))
Git workflow and deployment ([Git & GitHub](../../backend/git-workflow/), [Web App Deployment](../../backend/zeabur-deployment/))Git workflow and deployment ([Git & GitHub](../../backend/git-workflow/), [Web App Deployment](../../backend/zeabur-deployment/))
Learning ObjectivesLearning Objectives
After completing this project, you will be able to:After completing this project, you will be able to:
Read a PRD and extract a development task list for a data productRead a PRD and extract a development task list for a data product
Build a backend API service using Go (Gin or Fiber)Build a backend API service using Go (Gin or Fiber)
Design a complete pipeline for data ingestion, windowed aggregation, and alertingDesign a complete pipeline for data ingestion, windowed aggregation, and alerting
Keep backend data and frontend dashboards consistentKeep backend data and frontend dashboards consistent
Complete end-to-end integration and deliver a demo-ready data product prototypeComplete end-to-end integration and deliver a demo-ready data product prototype
Project OverviewProject Overview
You will build a Go traffic data analysis platform:You will build a Go traffic data analysis platform:
Module
Responsibility
Data Ingestion
Receive raw traffic events and store them
Data Aggregation
Calculate trends and congestion metrics by time window
Alerting
Generate alert records based on rules
Dashboard
Display trend charts, rankings, and alert lists on the frontend
💡 Tips Praktis💡 Pro Tip
The requirements document for this project is on GitHub: [View PRD](https://github.com/datawhalechina/easy-vibe/blob/main/docs/en/stage-2/assignments/traffic-data-visualization-go/PRD.md)The requirements document for this project is on GitHub: [View PRD](https://github.com/datawhalechina/easy-vibe/blob/main/docs/en/stage-2/assignments/traffic-data-visualization-go/PRD.md)
{ title: 'Requirements', description: 'Read PRD, define data sources, metric definitions, and alert rules' },{ title: 'Requirements', description: 'Read PRD, define data sources, metric definitions, and alert rules' },
{ title: 'Scaffold', description: 'Use AI to generate Go API service and frontend dashboard scaffold' },{ title: 'Scaffold', description: 'Use AI to generate Go API service and frontend dashboard scaffold' },
Part 1: Requirements AnalysisPart 1: Requirements Analysis
1.1 Read the PRD1.1 Read the PRD
Open the PRD document and answer these key questions:Open the PRD document and answer these key questions:
What is the data source? What fields does it contain?What is the data source? What fields does it contain?
What are the definitions of core metrics? (e.g., the specific criteria for "congestion")What are the definitions of core metrics? (e.g., the specific criteria for "congestion")
What are the alert rules? Should the first version use simple rules?What are the alert rules? Should the first version use simple rules?
What pages and charts does the dashboard include?What pages and charts does the dashboard include?
If the above questions don't have clear answers, don't start coding. Unclear requirements are the most common cause of rework.If the above questions don't have clear answers, don't start coding. Unclear requirements are the most common cause of rework.
1.2 Confirm Data Pipeline1.2 Confirm Data Pipeline
Part 2: Project ScaffoldingPart 2: Project Scaffolding
2.1 Generate Go API Service2.1 Generate Go API Service
Prompt reference:Prompt reference:
text
Based on the current PRD, help me generate a Go traffic data analysis platform scaffold. Requirements: 1. Use Gin or Fiber 2. Provide data ingestion API 3. Provide aggregation task skeleton 4. Provide dashboard and alerts API skeleton 5. Don't implement real complex analysis yet, just runnable structure
Data Ingestion API: Receive raw traffic events, write to databaseData Ingestion API: Receive raw traffic events, write to database
Data Aggregation: Aggregate by time window, calculate trends and congestion metricsData Aggregation: Aggregate by time window, calculate trends and congestion metrics
Alert Rules: Generate alert records based on thresholdsAlert Rules: Generate alert records based on thresholds
Dashboard API: Provide trend data, ranking data, alert listDashboard API: Provide trend data, ranking data, alert list
Frontend Dashboard: Trend charts, rankings, alert list pagesFrontend Dashboard: Trend charts, rankings, alert list pages
3.2 Module Self-Check3.2 Module Self-Check
Check Item
Verification Method
Data ingestion
Is raw data correctly stored in database?
Aggregation logic
Are trend and ranking metric calculations consistent?
Alert rules
Do alert trigger conditions match expectations?
Data consistency
Does the dashboard match the backend data?
API standards
Is there a unified response structure and error handling?
Part 4: Integration & LaunchPart 4: Integration & Launch
4.1 End-to-End Testing4.1 End-to-End Testing
At minimum, verify these scenarios:At minimum, verify these scenarios:
Ingest test data → Run aggregation task → Dashboard updatesIngest test data → Run aggregation task → Dashboard updates
Trigger alert condition → Alert record generated → Alert page displays itTrigger alert condition → Alert record generated → Alert page displays it
DeliverablesDeliverables
After completing this project, submit the following:After completing this project, submit the following:
[ ] Accessible live demo link[ ] Accessible live demo link
[ ] Source code repository link (with README)[ ] Source code repository link (with README)