Build a event-driven Notification Pipeline

Last updated: January 1, 2026

Quick Overview

Design a event-driven notification system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

Cockroach Labs
System Design
Software Engineer
Cockroach Labs
January 1, 2026
Software Engineer
System Design Round
System Design
Hard

2

13

2,747 solved


Design a event-driven notification system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.

This is a common system design question asked during System Design Round at Cockroach Labs. The interviewer expects you to demonstrate your ability to design large-scale distributed systems, make well-reasoned trade-offs, and communicate your thought process clearly. Cockroach Labs values engineers who can think about scalability from day one.

What the Interviewer Expects
  • Drive the design discussion proactively with minimal interviewer guidance
  • Perform detailed capacity estimation and use it to inform design decisions
  • Design for global scale with multi-region deployment and data consistency
  • Deep dive into 2-3 critical components with implementation-level detail
  • Address complex trade-offs: CAP theorem, eventual consistency, conflict resolution
  • Discuss operational excellence: deployment strategy, chaos engineering, SLOs/SLIs
  • Propose a phased rollout plan from MVP to full-scale system
Key Topics to Cover
Caching strategies (local, distributed, CDN)
Security and authentication
High-level architecture and component design
Database selection and data modeling
How to Approach This
  1. Start by clarifying functional and non-functional requirements with the interviewer.
  2. Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
  3. Draw a high-level architecture first, then deep dive into 1-2 critical components.
  4. Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
  5. Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
  • How would you migrate from a monolithic to a microservices architecture?
  • How would you handle schema migrations with zero downtime?
  • How would you handle a region-wide outage?
Practice a Similar Problem on Codemia

Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.

Solve on Codemia
Sample Answer
Requirements

Functional Requirements:

  1. Event Generation: The system must handle notifications generated from various sources (e.g., user actions, system events).
  2. Event Processing: Notifications mu...
Capacity Estimation

To handle millions of requests, we estimate the following:

  • Expected Peak Traffic: 10 million notifications per minute.
  • Total Notifications per Day: 10 million * 60 minutes * 24 hours = 14....

Submit Your Answer
Markdown supported

Related Questions