All learning paths

System design

Begin with one working service. Follow its requests, data, and failure paths before introducing more components.

Connect design decisions to a concrete service. Begin with requirements and request flow before adding more components.

2 available · 10 planned

Your learning path

Start with the linked lessons. The remaining topics are planned.

  1. Start with requirements

    Turn a short-link service brief into concrete behavior, quality targets, and acceptance scenarios.

    Available
  2. Trace the request flow

    Follow a redirect from client to cache and database, including expiry checks and dependency failures.

    Available
  3. Measure before scaling

    Use latency, throughput, and resource use to find the constraint.

    Planned
  4. Define the API contract

    Choose operations, responses, and useful error behavior.

    Planned
  5. Choose data models and indexes

    Let the access patterns shape storage decisions.

    Planned
  6. Separate cache retention from link validity

    Give cached data and business rules their own lifetimes.

    Planned
  7. Handle concurrency

    Reason about shared state and requests that overlap.

    Planned
  8. Run multiple application instances

    Identify what must be shared when one process becomes several.

    Planned
  9. Move work off the request path

    Use asynchronous work when the response can finish first.

    Planned
  10. Understand replication

    Consider copies, read behavior, and the cost of stale data.

    Planned
  11. Design for failures

    Set timeouts and decide what users see when a dependency fails.

    Planned
  12. Put the service design together

    Explain the complete system and its remaining trade-offs.

    Planned

A case study you can read now

Explore cache retention and link validity through a Go URL shortener.

Cache Expiry vs Link Expiry: Getting a Go URL Shortener Right