Skip to main content

Go Track

Weekly Goals​

  • System Design
    • Learn structured approach to system design interviews.
    • Design scalable REST APIs for realistic services.
    • Understand service boundaries, API gateways, load balancing.
  • Backend Practice
    • Map system designs to Go projects.
  • DSA
    • Maintain 2–3 problems/day.
  • Theory
    • Tie HTTP, networking, DB concepts into system design.

Use together with:

Weekly Overview Table​

DayFocus
1System design interview framework
2Designing scalable REST APIs (generic patterns)
3API gateway, service boundaries, versioning
4Design: Note-taking / Task management backend
5Design: URL shortener (full system)
6Connect system design to existing project
7Weekly review & one full mock design

Day 1 – System Design Interview Framework​

4-Hour Plan​

  • Block 1 (Concepts – 60–75 min)

    • Learn framework:
      • Clarify requirements.
      • Define APIs and core use cases.
      • High-level components and data flow.
      • Storage, caching, queues.
      • Scalability, reliability, security.

  • Block 2 (Template Creation – 60 min)

    • Create system design template in markdown.

  • Block 3 (DSA – 60 min)

    • 2–3 problems.

  • Block 4 (Review – 30 min)

    • Save template for reuse.

6-Hour Plan​

  • Add:
    • Practice (60 min): Sketch design for feature flag service.

Day 2 – Designing Scalable REST APIs​

4-Hour Plan​

  • Block 1 (Concepts – 60–75 min)

    • Study patterns:
      • Resource naming.
      • Pagination, filtering, sorting.
      • Idempotency.
      • Error handling.

  • Block 2 (Design Exercises – 60 min)

    • Design APIs for:
      • User management.
      • Auth session management.

  • Block 3 (DSA – 60 min)

    • 2–3 problems.

  • Block 4 (Review – 30 min)

    • Document API design guidelines.

6-Hour Plan​

  • Add:
    • Refinement (60 min): Compare with public APIs.

Day 3 – API Gateway, Service Boundaries, Versioning​

4-Hour Plan​

  • Block 1 (Concepts – 60–75 min)

    • Learn:
      • Monolith vs microservices.
      • API gateway responsibilities.
      • Service boundaries.
      • Versioning strategies.

  • Block 2 (Diagramming – 60 min)

    • Draw diagrams.

  • Block 3 (DSA – 60 min)

    • 2–3 problems.

  • Block 4 (Review – 30 min)

    • Identify service boundaries in projects.

6-Hour Plan​

  • Add:
    • Service decomposition (60 min).

Day 4 – Design: Note-Taking Backend​

4-Hour Plan​

  • Block 1 (Requirements – 45–60 min)

    • Clarify requirements.

  • Block 2 (Design – 90 min)

    • APIs, data model, architecture.

  • Block 3 (Review – 30–45 min)

    • Where to cache, background jobs.

6-Hour Plan​

  • Add:
    • Implementation mapping (60 min).

Day 5 – Design: URL Shortener​

4-Hour Plan​

  • Block 1 (Requirements – 45–60 min)

    • Functional and non-functional requirements.

  • Block 2 (Design – 90 min)

    • API design, data model, components.

  • Block 3 (Review – 30–45 min)

    • Code generation, caching strategy.

6-Hour Plan​

  • Add:
    • Scaling considerations (60 min).

Day 6 – Connect Design to Project​

4-Hour Plan​

  • Block 1 (Mapping – 60–75 min)

    • Map components to Go modules.

  • Block 2 (Implementation Planning – 60 min)

    • Create implementation roadmap.

  • Block 3 (DSA – 60 min)

    • 2–3 problems.

  • Block 4 (Review – 30 min)

    • Update README with architecture diagram.

6-Hour Plan​

  • Add:
    • Code changes (60 min).

Day 7 – Weekly Review & Mock Design​

4-Hour Plan​

  • Block 1 (Review – 60–75 min)

    • Revisit framework, API patterns, service boundaries.

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

    • Time-box: 45–50 min design.

  • Block 3 (DSA – 30–45 min)

    • 1–2 problems.

6-Hour Plan​

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