Why this matters
- send(userId, templateId, payload) across channels
- Scope — what "Channels" covers inside Notification Service and what it does not
- Scope — what "Retry" covers inside Notification Service and what it does not
- Scope — what "Templates" covers inside Notification Service and what it does not
- In-memory systems test data structures + thread safety together.
SubjectnotifyObservers()
Observer A
Observer B
Observer C
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
- send(userId, templateId, payload) across channels
- Channels: email, SMS, push — Strategy per channel
- Retry failed deliveries with backoff
- Template engine substitutes variables
- Idempotent send with deduplication key
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 Notification Service as a production-ready in-process service. Read requirements point-by-point before drawing classes.
Requirements
Points to cover
- send(userId, templateId, payload) across channels
- Channels: email, SMS, push — Strategy per channel
- Retry failed deliveries with backoff
- Template engine substitutes variables
- Idempotent send with deduplication key
Channels
Points to cover
- Scope — what "Channels" covers inside Notification Service 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
Retry
Points to cover
- Scope — what "Retry" covers inside Notification Service 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
Templates
Points to cover
- Scope — what "Templates" covers inside Notification Service 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
// CampusOS — NotificationService facade (keep thin)
public final class NotificationServiceService {
private final NotificationServiceRepository repository;
public NotificationServiceService(NotificationServiceRepository 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.
- Requirements — review this slice before mock interviews.
- Channels — review this slice before mock interviews.
- Retry — review this slice before mock interviews.
- Templates — 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.