Find a lesson, question or project

Start typing to search published content and planned structures.

↑ ↓ moveEnter openEsc close

What you will build

A short-link service whose engineering decisions remain visible.

The finished system accepts a long URL, creates a short code, redirects readers quickly, resists abuse, scales across instances and exposes enough operational signals to debug failures.

Architecture overview

Follow a request across the stack.

Milestone sequence / 09

Build one layer at a time.

Open the published resources for each milestone and use the planned list as a preview of what is coming next.

  1. 01

    Model the domain using LLD

    Define links, aliases, expiry rules, responsibilities and extension points before choosing infrastructure.

    entities and value objectsinvariantsservice boundaries

    Published resources

    Planned resources

    • URL shortener domain model walkthroughPlanned
  2. 02

    Implement the core logic in Java

    Create short codes, resolve destinations and enforce domain rules with testable Java classes.

    modern Javacollectionserror handling

    Published resources

    Planned resources

    • Core service implementation and unit testsPlanned
  3. 03

    Expose REST APIs using Spring Boot

    Create endpoints for shortening and redirecting while keeping transport concerns outside the domain model.

    request lifecyclecontrollers and servicesHTTP contracts

    Published resources

    Planned resources

    • URL API contract and controller implementationPlanned
  4. 04

    Add validation, persistence and tests

    Store link mappings safely, validate requests and protect behavior with focused tests.

    validationrepository boundariesintegration testing

    Published resources

    No complete resource is linked yet.

    Planned resources

    • Persistence modelPlanned
    • Validation and testing strategyPlanned
  5. 05

    Add caching and rate limiting

    Reduce redirect latency and protect write endpoints without hiding freshness or failure behavior.

    cache-asideevictionrate limiting

    Published resources

    Planned resources

    • Cache integrationPlanned
    • Token bucket rate limiterPlanned
  6. 06

    Reason about distributed scaling

    Estimate demand and decide how identifiers, storage, caches and redirects behave across many instances.

    capacity estimationkey generationreplication and failure

    Published resources

    Planned resources

    • Failure-mode review and scaling worksheetPlanned
  7. 07

    Package the application with Docker

    Build a small, reproducible container image with a clear runtime boundary.

    image layersmulti-stage buildsnon-root runtime

    Published resources

    Planned resources

    • Project Dockerfile and local Compose environmentPlanned
  8. 08

    Deploy it using Kubernetes

    Run replicated instances behind stable networking with explicit resources and rollout behavior.

    DeploymentsServicesconfiguration and rollouts

    Published resources

    Planned resources

    • Deployment, Service and configuration manifestsPlanned
  9. 09

    Add health checks, metrics, logging and tracing

    Make correctness, latency and failure visible before the service reaches production.

    health signalsstructured logsmetrics and traces

    Published resources

    No complete resource is linked yet.

    Planned resources

    • OpenTelemetry instrumentationPlanned
    • Service dashboard and alert reviewPlanned