Queue vs Stack When to Use Which in DSA Python - Complexity Comparison
We want to understand how fast operations happen in queues and stacks.
Which one is better for different tasks and why?
Analyze the time complexity of basic queue and stack operations.
class Stack:
def __init__(self):
self.items = []
def push(self, item):
self.items.append(item)
def pop(self):
return self.items.pop()
class Queue:
def __init__(self):
self.items = []
def enqueue(self, item):
self.items.append(item)
def dequeue(self):
return self.items.pop(0)
This code shows how stack and queue add and remove items.
Look at the main actions that repeat when using these structures.
- Primary operation: Adding and removing items.
- How many times: Each operation happens once per item added or removed.
- Stack uses append and pop from the end (fast).
- Queue uses append at end and pop from start (pop(0)) which shifts items.
Adding or removing one item in stack stays fast no matter how many items.
Removing from queue by pop(0) takes longer as more items are in the queue.
| Input Size (n) | Stack pop operations | Queue dequeue operations |
|---|---|---|
| 10 | 10 fast steps | 10 steps with small shifts |
| 100 | 100 fast steps | 100 steps with bigger shifts |
| 1000 | 1000 fast steps | 1000 steps with large shifts |
Stack operations stay quick as size grows; queue dequeue slows down with size.
Time Complexity: O(1) for stack push/pop, O(n) for queue dequeue using list pop(0)
Stack operations take constant time; queue dequeue takes longer as queue grows.
[X] Wrong: "Queue dequeue is always fast like stack pop."
[OK] Correct: Removing from the front of a list shifts all other items, making it slower as size grows.
Knowing when stack or queue operations are fast helps you pick the right tool for the job in coding challenges and real projects.
What if we used a linked list for the queue instead of a list? How would the time complexity change?