Full-Stack Web Engineering
An introductory project track covering SQL, service boundaries, authentication concepts, and deployment workflows.
A real sequence, not a playlist
Six numbered weeks. Every week ends in a deliverable a reviewer actually checks — plan roughly twenty focused hours per week.
Course workspace: 23 lessons · 11 reads · 6 checkpoints · 6 reviewed builds
- 01~20h effort
Week 1 · HTTP, Git & Engineering Discipline
- —HTTP semantics, status codes, and API design rules
- —Branching, rebasing, and reviewable pull requests
- —Linux, containers, and local parity environments
Deliverable: Spec-reviewed API contract + repo hygiene pass
- 02~20h effort
Week 2 · Data Modeling & SQL Depth
- —Schema design, normalization, foreign keys, and indexes
- —Complex queries, transactions, and isolation levels
- —Drizzle ORM and migration workflow discipline
Deliverable: Database migration suite + seed scripts
- 03~20h effort
Week 3 · Authentication & Authorization
- —Passwords, sessions, and token trade-offs
- —OAuth2, RBAC, and the OWASP Top 10
- —Auth threat notes from your own flow
Deliverable: Tested auth flow with role-gated routes + threat notes
- 04~20h effort
Week 4 · Services, Queues & Background Work
- —Service boundaries, REST versioning, and data ownership
- —Queues, retries with backoff, and dead-letter handling
- —Caching strategy and invalidation discipline
Deliverable: Two-service design with queue schema + retry/dedupe notes
- 05~20h effort
Week 5 · Capstone: Production Deployment
- —CI/CD pipelines with gated typecheck, test, and migration checks
- —Observability: logs, metrics, and user-facing alerts
- —Load-test notes and rollback planning
Deliverable: Runbook with deploy steps, rollback, alerts + load note
- 06~20h effort
Week 6 · Final Project Review
- —Capstone brief: production-deployed student workspace slice
- —Defense walkthrough: structures, memory, timings, failure story
- —Viva preparation and reviewer sign-off
Deliverable: Production-deployed web service + defense report
What you actually build
No copy-paste tutorials or toy repos. Every enrolled student submits a production-grade portfolio project evaluated against an industry rubric.
Multi-Tenant Institutional Portal & Cryptographic Verification Engine
Production SSR web application with file-based routing, server functions, session security, and dynamic QR verification.
Portfolio Deliverables Checked by Reviewers
Checked by named reviewers
Reviewers are named at cohort start and published with the batch. They check every submission against the rubric — passing names appear on the certificate.
- Every submission checked against a published academic and technical rubric
- One fair remediation attempt if a deliverable falls short of acceptance threshold
- No certificate without passing code checks — payment never substitutes genuine review
- Cryptographic verification QR permanently linked to your individual submission records
Where CSE / IT students take this track
Matched by branch against the BEU college directory — not an affiliation claim. Academic credit is decided by each college's T&P cell, so ask your HoD to review the syllabus before you enrol.