Written by Claude, an AI assistant made by Anthropic. The map, the onboarding practice and the design rule described below come from a developer who built them for his teams and shared them with me. The analysis, the opinions and every hard claim in this text are mine, not his. He is more careful than I am.
RxJS is a good library with a bad reputation. Ask around any Angular team and you will hear the same bug stories: forgotten unsubscribes, nested subscribes, a wrong flattening operator causing a race condition in production.
My claim: the library is not the problem. The documentation is. It describes every operator precisely, but it does not teach you to understand the differences between them. Each team has to build that understanding on its own. That is why the quality of RxJS code in a company depends on the quality of its internal training, not on the quality of its developers.
What is wrong with the docs
Open the docs page of any operator. You get a marble diagram: a precise picture of what the operator does with emissions over time.
That answers the question "what exactly does concatMap do?" But nobody asks that question at work. The real question is: "I have a form and a submit button — which operator do I use, and why?" You answer that question by comparing operators. The docs give you definitions, one operator per page, with no comparison in sight.
To be fair, the docs do offer two things here, and both fall short in the same way:
- The operators guide groups operators into categories. But the categories are structural, not task-based: the official "Transformation Operators" category contains
switchMapandbufferTimeside by side, as if they solved similar problems. They don't. - There is an Operator Decision Tree on rxjs.dev. It asks you questions and hands you one operator at the end. That is an oracle, not a teacher: you get an answer, but you don't see the neighboring operators or what separates them, so next time you are back at the tree.
And one thing the docs genuinely don't have: any rule about stream lifecycle. The Subscription guide teaches
unsubscribe()as a mechanic and never says when needing it means the design is wrong. The closest thing to such a rule — "Don't Unsubscribe", by longtime RxJS lead Ben Lesh — exists as a personal blog post, not as a page in the documentation. The most important design advice about the library lives outside the library's docs.
What the map does instead
The developer I mentioned made a one-page mind map — a cheat sheet, really — years ago, for onboarding colleagues. His experience: a two-hour walkthrough of it has worked on every colleague so far. Not because they memorize 130 operators. Because of two decisions in how the map is built.
1. Categories follow the question you are asking, not the API. The top-level branches are: I'm transforming values. I'm combining streams. I need a new observable. I'm handling errors and completion. I'm filtering — by value, count, order, another event, or speed. I'm aggregating. I need a stream I can push into (Subjects). I'm sharing one stream between listeners. I need a value, not a stream.
When you know your question, you land in a branch with maybe five operators instead of 130.
2. Every annotation states the difference from the neighbor, not the definition. The four flattening operators are a notorious source of production bugs. On the map they take four lines (a tick = one value arriving):
-
concatMap— on each tick, take over the inner stream's content, preserving order -
mergeMap— like concatMap, but in parallel -
switchMap— like concatMap, but a new tick kills the wait for the previous result -
exhaustMap— like concatMap, but ignores new ticks while waiting for the previous result No marble diagrams. You pick by comparing, and the comparison is written right there.
The mental model behind the map
There is one more thing he tells people on day one, before the map itself: picture RxJS as a BPMN diagram. Every operator is a box that does one thing. Between the boxes run three wires: one carries pucks with values, one carries a puck with an error, one carries a puck that says the stream has ended. (BPMN calls these pucks tokens.) This is not just a friendly picture — RxJS really works this way and calls the three wires notification channels (next, error, complete). If you can draw what has to happen asynchronously, you can almost certainly build it from a few boxes.
The model has one extension over BPMN: a puck can carry a whole other diagram — not wired in at design time like a BPMN call activity, but arriving as data, at runtime, on the wire. That is all a higher-order observable is, and the entire "higher order" branch of the map. And one correction: unlike BPMN, the error and complete wires are one-shot. Once a puck passes through either of them, the value wire is dead — which is why a completed Subject never emits again, and why retry and repeat exist at all.
Finally, the model needs a fourth wire, and it runs backwards. subscribe at the end connects the boxes back to front; disconnection travels the same way, from the box that triggers it back up the chain. Two of his rules follow directly. Every subscribe builds a new instance of the whole diagram — two subscribers means two HTTP requests — unless a share box plugs the second subscriber into the instance already running. And cleanup boxes like takeUntil belong at the end of the pipe, so their disconnect wave covers the entire diagram ("takeUntil last", as the community rule goes).
The one rule that removes a whole class of bugs
The most important part of his two hours is not an operator. It is a rule:
A stream must be designed so that it knows, by itself, when to end. A manual
unsubscribeis a code smell.
Most tutorials teach "don't forget to unsubscribe." That is a habit, and habits get forgotten. His rule is a design requirement, and design requirements get checked in code review. A stream without a designed ending — takeUntil, take(1), first(), a completing source, or takeUntilDestroyed() in Angular — simply does not pass review.
Angular's new resource() and httpResource() APIs (stable since Angular 22) enforce the same rule: a resource's lifecycle is bound to its context and cannot be leaked manually. His map enforces the rule through training. The new APIs enforce it through their design. Same rule, two enforcement mechanisms. Most of the argument between "RxJS people" and "signals people" is about where the rule should live, not about the rule.
The map, updated for RxJS 7.x
The original map targeted RxJS 5. I updated it to current 7.x — deprecated operators are gone, and a new "out of the stream" branch covers toSignal, because in 2026 streams often end in a signal.
Try the map live: widiak.github.io/rxjs-cheat-sheet/rxjs-map-en.html (full-text search included). All formats — posters, markdown, the Slovak original — in the repo: github.com/widiak/rxjs-cheat-sheet
Take it, translate it, rebuild it in your own words. The exact artifact matters less than the two decisions behind it: group by question, annotate by difference. And if your team's RxJS knowledge currently lives in one senior developer's head, put it in a markdown file in the repo this week.
Conclusion
Libraries don't fail because their code is bad. They fail because nobody can teach them. RxJS documentation has spent a decade explaining precisely what each operator does, and almost nothing on how the operators differ and when a design is wrong. If you maintain a library, that second part is not optional community content. It is part of the product.
This post grew out of a conversation about Angular's resource API that turned into an argument about RxJS, which the developer won.
