Skip to main content

Go Track

Weekly Goals​

  • System Design
    • Design Uber/Swiggy-like system.
    • Design notification system with multiple channels.
  • Backend Practice
    • Tie designs to Go projects.
  • DSA
    • Continue mixed problems (graphs).
  • Theory
    • Apply CAP, consistency, eventual consistency.

Use together with:

Weekly Overview Table​

DayFocus
1Uber/Swiggy requirements & basics
2Uber/Swiggy – location, matching, pricing
3Notification system – requirements & channels
4Notification system – scaling, retries, DLQ
5System design trade-offs & consistency
6Map designs to project implementations
7Weekly review & timed design mock

Day 1 – Uber/Swiggy Requirements & Basics​

4-Hour Plan​

  • Block 1 (Requirements – 60–75 min)

    • Clarify actors, core flows, non-functional requirements.

  • Block 2 (High-Level Design – 60 min)

    • Identify services.

  • Block 3 (DSA – 60 min)

    • 2–3 graph/shortest path problems.

  • Block 4 (Review – 30 min)

    • Document component list.

6-Hour Plan​

  • Add:
    • Data model brainstorming (60 min).

Day 2 – Uber/Swiggy: Location, Matching, Pricing​

4-Hour Plan​

  • Block 1 (Design Deep Dive – 60–75 min)

    • Driver locations, matching algorithm, pricing.

  • Block 2 (Architecture – 60 min)

    • Draw data flow.

  • Block 3 (Trade-offs – 60 min)

    • CAP trade-offs for location data.

  • Block 4 (Review – 30 min)

    • Summarize matching approach.

6-Hour Plan​

  • Add:
    • Scaling considerations (60 min).

Day 3 – Notification System: Requirements & Channels​

4-Hour Plan​

  • Block 1 (Requirements – 60–75 min)

    • Functional and non-functional requirements.

  • Block 2 (Design – 60 min)

    • Components: API, queue, workers, DB.

  • Block 3 (DSA – 60 min)

    • 2–3 problems.

  • Block 4 (Review – 30 min)

    • Draw notification pipeline.

6-Hour Plan​

  • Add:
    • Payload modeling (60 min).

Day 4 – Notification System: Scaling, Retries, DLQ​

4-Hour Plan​

  • Block 1 (Concepts – 60–75 min)

    • Retries, DLQ, idempotency.

  • Block 2 (Design Deep Dive – 60 min)

    • Extend design with DLQ, status tracking.

  • Block 3 (DSA – 60 min)

    • 2–3 problems.

  • Block 4 (Review – 30 min)

    • Monitoring and alerting.

6-Hour Plan​

  • Add:
    • LLD sketch (60 min).

Day 5 – System Design Trade-Offs & Consistency​

4-Hour Plan​

  • Block 1 (Theory Integration – 60–75 min)

    • Revisit CAP, ACID vs BASE.
    • Apply to Uber/Swiggy, notification system.

  • Block 2 (Trade-off Writing – 60 min)

    • Consistency-critical vs availability-critical components.

  • Block 3 (DSA – 60 min)

    • 2–3 problems.

  • Block 4 (Review – 30 min)

    • Key trade-offs for interview.

6-Hour Plan​

  • Add:
    • Practice explanation (60 min).

Day 6 – Map Designs to Project Implementations​

4-Hour Plan​

  • Block 1 (Mapping – 60–75 min)

    • Map components to Go modules.

  • Block 2 (Implementation Planning – 60 min)

    • Create backlog.

  • Block 3 (DSA – 60 min)

    • 2–3 problems.

  • Block 4 (Review – 30 min)

    • Update project notes.

6-Hour Plan​

  • Add:
    • Small implementation (60 min).

Day 7 – Weekly Review & Timed Design Mock​

4-Hour Plan​

  • Block 1 (Review – 60–75 min)

    • Revisit designs.
    • Update skill gap template.

  • Block 2 (Timed Design Mock – 60–75 min)

    • 45–50 min design.

  • Block 3 (DSA – 30–45 min)

    • 1–2 problems.

6-Hour Plan​

  • Add:
    • Self-critique (45–60 min).