Somewhat. This is true for the drag-and-drop interface and representation, but nodes here are an implementation detail IMO. Nodes are a subset of
visual programming, and well-suited for representing functional and data-oriented processing pipelines.
In turn, these programming paradigms are well suited to hardware acceleration and distributed/multithreaded pipelines.
The underlying edition approach is called "non-destructive editing", as you can always remove some operations to find the original again.
When it comes to visual programming, the first example that comes to my mind is labview, which I find very unwieldy to work with. As a programmer, node editors are one of the very few visual programming methods I'm comfortable using (at least as long as the graphs stay relatively small).