Data Stream as Disjoint Intervals
Expert Answer & Key Takeaways
# System & Data Structure Design
Design problems in DSA interviews test your ability to translate requirements into a functional, efficient, and maintainable class structure. Unlike standard algorithmic problems, the focus here is on State Management and API Design.
### Core Principles
1. Encapsulation: Keep data private and expose functionality through well-defined methods.
2. Trade-offs: Every design choice has a cost. Is it better to have read and write, or vice versa?
3. State Consistency: Ensure that your internal data structures (e.g., a Map and a List) stay in sync after every operation.
### Common Design Patterns
#### 1. HashMap + Doubly Linked List (DLL)
The "Gold Standard" for caching (LRU/LFU).
```text
[Head] <-> [Node A] <-> [Node B] <-> [Node C] <-> [Tail]
^ ^ ^ ^ ^
(MRU) (Data) (Data) (Data) (LRU)
```
- HashMap: Provides lookups for keys to their corresponding nodes.
- DLL: Provides addition/removal of nodes at both ends, maintaining the order of access.
#### 2. Amortized Analysis (Rebalancing)
Commonly used in Queue using Stacks or Dynamic Arrays.
- Instead of doing heavy work on every call, we batch it. Pushing to a stack is , and "flipping" elements to another stack happens only when necessary, averaging per operation.
#### 3. Ring Buffers (Circular Arrays)
Used for fixed-size memory management (e.g., Circular Queue, Hit Counter).
```text
[0] [1] [2] [3] [4] [5]
^ ^ ^
Head (Data) Tail
(Pops) (Next Push)
```
- Use `(index + 1) % capacity` to wrap around the array.
#### 4. Concurrency & Thread Safety
For "Hard" design problems (e.g., Bounded Blocking Queue).
- Use Mutexes (Locks) to prevent data races.
- Use Condition Variables (`wait`/`notify`) to manage producer-consumer logic efficiently without busy-waiting.
### How to Approach a Design Problem
1. Identify the API: What methods do you need to implement? (`get`, `put`, `push`, etc.)
2. Define the State: What variables represent the current state? (Size, Capacity, Pointers).
3. Choose the Data Structures: Select the combination that minimizes time complexity for the most frequent operations.
4. Dry Run: Trace the state changes through a sequence of operations based on your chosen structure.
Data Stream as Disjoint Intervals
Given a data stream input of non-negative integers , summarize the numbers seen so far as a list of disjoint intervals.
Requirement
addNum(val): Add integer to the stream.getIntervals(): Return the summary as a list of intervals.
Examples
Input: addNum(1), getIntervals(), addNum(3), getIntervals(), addNum(2), getIntervals()
Output: [[1, 1]], [[1, 1], [3, 3]], [[1, 3]]
Approach 1
Level I: List of Numbers + Rebuild on Query
Intuition
Store all individual numbers in a
Set to handle duplicates. For getIntervals, convert the set to a sorted list and iterate through it to form intervals whenever numbers are not consecutive.⏱ Add: O(1), Get: O(N log N) for sorting.💾 O(N).
Detailed Dry Run
Input: 1, 3, 2. Set: {1, 2, 3}. Sorted: [1, 2, 3]. Intervals: [[1, 3]].
Approach 2
Level II: Sorted List (Manual Merging)
Intuition
Maintain a list of disjoint intervals sorted by start time. For
addNum, find the insertion spot and check if it can merge with neighbor intervals. This is due to list shifting.⏱ Add: O(N), Get: O(1).💾 O(N).
Approach 3
Level III: Balanced BST / TreeMap
Intuition
Use a
TreeMap to store intervals as start -> end. When a new number x is added, find the interval that ends just before it and the one that starts just after it. Merge them if possible.⏱ Add: O(log N), Get: O(N).💾 O(N).
Course4All Technical Board
Verified ExpertSenior Software Engineers & Algorithmic Experts
Our DSA content is authored and reviewed by engineers from top tech firms to ensure optimal time and space complexity analysis.
Pattern: 2026 Ready
Updated: Weekly
Found an issue or have a suggestion?
Help us improve! Report bugs or suggest new features on our Telegram group.