Design a Monitoring Service
Last updated: October 23, 2025
Quick Overview
Design a distributed monitoring system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Atlassian
System Design
Software Engineer
Atlassian
October 23, 2025Software Engineer
Technical Screen
System Design
Easy
23
8
4,477 solved
Design a distributed monitoring system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Atlassian asks this during the Technical Screen to assess your architectural thinking. They want to see how you decompose a complex problem, choose appropriate technologies, and reason about failure modes. Strong candidates proactively discuss monitoring, alerting, and operational concerns.
What the Interviewer Expects
- Clearly define functional and non-functional requirements
- Propose a reasonable high-level architecture with core components
- Choose appropriate data storage solutions with basic justification
- Discuss basic scaling strategies (horizontal scaling, caching)
- Identify potential bottlenecks and suggest simple solutions
Key Topics to Cover
Load balancing and horizontal scaling
High-level architecture and component design
Message queues and async processing
Monitoring, logging, and alerting
Security and authentication
How to Approach This
- Start by clarifying functional and non-functional requirements with the interviewer.
- Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
- Draw a high-level architecture first, then deep dive into 1-2 critical components.
- Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
- Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
- What happens if one of your database nodes goes down?
- What monitoring and alerting would you set up on day one?
- How would you optimize costs as the system scales?
- How would you implement rate limiting to protect the system?
Practice a Similar Problem on Codemia
Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.
Solve on CodemiaSample Answer
Requirements
- Functional Requirements:
- The system must collect metrics from various services (CPU usage, memory, network traffic) at a minimum frequency of 1 second.
- Users must be able to query hi...
Capacity Estimation
- Assuming each service generates about 1 metric per second, monitoring 1 million services would yield 10 million metrics per minute.
- Each metric could have an average size of 100 bytes (timestamp...
Submit Your Answer
Markdown supported