Queue

Lesson notes

Overview

First in, first out: the structure behind print jobs, buffers and breadth-first search. This topic is rated beginner and is number 20 of 117 in Computer Science. Core ideas and first intuitions. No prior knowledge needed.

What you are seeing

The panel above shows an interactive animation of the idea. Every slider changes one quantity so you can see its effect on the outcome. The animation is drawn live from the model, so everything you see responds to the sliders. Press Space to pause, use Restart to replay from the start, and change the speed to slow down quick events.

In depth

A queue is a first-in, first-out structure: items are added at the back, enqueue, and removed from the front, dequeue, each in O(1) with a suitable implementation. It models a line of customers. Operating systems use queues for print jobs and task scheduling, networks use them to buffer packets, and breadth-first search relies on one. Variants include double-ended queues and priority queues.

Reading the relationship

The expression "enqueue / dequeue in O(1)" is a compact summary of the idea. It uses the symbols e, n, q, u, d, i; name what each one stands for before you start. Notice that it contains a ratio, so increasing the denominator makes the result smaller. Then use the sliders to see how changing one quantity changes the others.

A guided exploration

1. Run the animation once with the default settings and describe in words what happens. 2. Change one slider at a time and note which quantity responds most. 3. Push each slider to its extreme and decide whether the result still makes sense.

Try this

Start by only moving one slider at a time. Say aloud what you expect, then check.

Common pitfalls

Test small inputs by hand and then the largest ones. Off-by-one errors and forgetting how cost grows with input size are the most common traps.

How it connects

It builds on “Stack”, the topic before it in Computer Science. Once you are comfortable, continue with “Binary Search Tree”.

Why it matters

Computing ideas decide how fast, how safely and how well software can solve problems.