The only difference is which extreme sits at the root. A min-heap keeps its smallest value on top, and a max-heap keeps its largest. Both obey the same shape rule and the same parent-child ordering, just flipped.
In a min-heap, every parent is smaller than or equal to its children. In a max-heap, every parent is larger than or equal to its children. Neither orders siblings, so you cannot read a sorted list off the array.
You pick based on what you pull first. To take the cheapest task next, use a min-heap. To take the highest-scoring item, use a max-heap. Peeking at the top costs O(1), and removing it costs O(log n) either way.
If your library only ships one kind, negating numeric keys fakes the other.
This answer doesn't lend itself to a diagram - it reads best . No credits were charged.
Why there's no diagram: “”
The interactive diagram is below the answer - jump to diagram ↓ · Below it, the related concept . Jump to it ↓
The diagram below the answer is the concept . Jump to it ↓