PrepZone Logo
PrepZone
Start Free Trial

Design StackOverflow Clone

Questions, answers, votes, reputation, and tags.

Expert18 min read

Read these first

Why this matters

  • Post questions with title, body, and tags
  • Scope — what "Core entities" covers inside StackOverflow Clone and what it does not
  • Scope — what "Voting" covers inside StackOverflow Clone and what it does not
  • Scope — what "Reputation rules" covers inside StackOverflow Clone and what it does not
  • Platform problems test entity graphs and derived state (reputation, balance).
Dependency direction
Controller / FacadeHTTP or API entry
Serviceuse cases, orchestration
Domainentities, rules, invariants
Repositorypersistence port
Dependencies point inward — domain never imports infrastructure.

CampusOS context

CampusOS is the fictional smart-campus platform used across this track. Treat this module as a real product slice:

Context

  • Belongs to CampusOS — same naming and design vocabulary as parking, library, and booking modules
  • Scope is one JVM — persistence is in-memory or behind a repository interface
  • Goal is a class diagram + core Java that an interviewer can follow in 35–45 minutes
  • Extension paragraph at the end links to System Design when scale exceeds one process

Requirements snapshot

Functional requirements

  • Post questions with title, body, and tags
  • Post answers; accept one answer per question
  • Upvote/downvote questions and answers
  • Reputation increases on upvotes; decreases on downvotes
  • Comments on questions and answers (optional scope)
  • Search by tag and keyword

Non-functional requirements

  • Single JVM, in-process design for this LLD article
  • Core flows testable with in-memory repositories
  • Extension points for new rules without editing central god classes
  • Clear public API on facade/service layer
  • CampusOS extension links to System Design when scale demands distribution

Overview

This CampusOS module designs StackOverflow Clone as a production-ready in-process service. Read requirements point-by-point before drawing classes.

Requirements

Points to cover

  • Post questions with title, body, and tags
  • Post answers; accept one answer per question
  • Upvote/downvote questions and answers
  • Reputation increases on upvotes; decreases on downvotes
  • Comments on questions and answers (optional scope)
  • Search by tag and keyword

Core entities

Points to cover

  • Scope — what "Core entities" covers inside StackOverflow Clone and what it does not
  • Classes — name 2–4 classes/interfaces responsible for this slice
  • Flow — step-by-step: trigger → validation → state change → side effect
  • Edge cases — invalid input, concurrent access, empty state, timeout
  • Pattern — Strategy, State, Observer, or Facade if it fits naturally
  • Test hook — one scenario an interviewer will ask you to walk through

Voting

Points to cover

  • Scope — what "Voting" covers inside StackOverflow Clone and what it does not
  • Classes — name 2–4 classes/interfaces responsible for this slice
  • Flow — step-by-step: trigger → validation → state change → side effect
  • Edge cases — invalid input, concurrent access, empty state, timeout
  • Pattern — Strategy, State, Observer, or Facade if it fits naturally
  • Test hook — one scenario an interviewer will ask you to walk through

Reputation rules

Points to cover

  • Scope — what "Reputation rules" covers inside StackOverflow Clone and what it does not
  • Classes — name 2–4 classes/interfaces responsible for this slice
  • Flow — step-by-step: trigger → validation → state change → side effect
  • Edge cases — invalid input, concurrent access, empty state, timeout
  • Pattern — Strategy, State, Observer, or Facade if it fits naturally
  • Test hook — one scenario an interviewer will ask you to walk through
Java
// CampusOS — StackoverflowClone facade (keep thin)
public final class StackoverflowCloneService {
    private final StackoverflowCloneRepository repository;

    public StackoverflowCloneService(StackoverflowCloneRepository repository) {
        this.repository = repository;
    }

    /** Orchestrate: validate → domain rules → persist → return result */
    public Result handle(Request request) {
        request.validate();
        var domain = DomainModel.from(request);
        domain.applyRules();
        return repository.save(domain);
    }
}

Quick recall

Everything you need if you only revisit this box.

  1. Requirements — review this slice before mock interviews.
  2. Core entities — review this slice before mock interviews.
  3. Voting — review this slice before mock interviews.
  4. Reputation rules — review this slice before mock interviews.

CampusOS extension

When this outgrows one JVM

  • Shard inventory or state by campus ID or geographic region
  • Push notifications, payments, and search to dedicated services (System Design track)
  • Use message queues for async side effects (email, analytics)
  • The class diagram you drew here becomes one box on the HLD architecture diagram

Test yourself

Answer these before moving on — recall is what makes it stick.