A Linux pipe is a form of redirection of standard output of one command into the standard input of another command. This process can then be used in a kind of chain actually, which can result in a kind of pipe where once command creates some kind of raw form of data that then gets passed into another the preforms some kind of first action on this raw data, and then so one with the next command and so forth as many times as needed. So then piping allows for breaking something down into a bunch of steps where one program does just one thing and then the output of that command is then passed on to another command that accepts that result as input to which it then uses to preform yet another result.
There is also Linux redirection that is similar to a Linux pipe, but works a little differently. With Linux pipes two commands can run in parallel with each other, and data is transferred in a per buffer basis. With Linux redirection one command must complete, before the next can start.
With a Linux pipe I can pipe the output of one command to another, and then from the output of that to yet another command. For example I can use the ps command to get a list of all processes running at the moment, and then I can pipe that list to grep where I can filter everything but instances of kworker. I can then pipe the output yet again, say I just want kworker events listed, for this I can pipe once more to grep yet again to the that list.
There is piping the output of one command to the standard input of another command, but what if I want to pipe the output of a command not to the standard input of another, but to use that output as arguments for another command. This subject deserves a post of its own, and I did just that when writing my post on a Linux command know as xargs. I will not be getting into the use of this command in detail then as I have done that in that post, but I should at least mention a basic example of it here in my post on piping in general.
So say I have a text file called file_list.txt that is a list of file names like this that are also in the same working directory
file1.txt just contains the text foo
file2.txt just contains the text bar plus a like break at the end
I can then use the cat command to read the file_list.txt file and then pipe that text to the Linux xargs command, with that the file names are then used as arguments for the cat command again. As a result the text of file1.txt and file2.txt are concatenated into a single stream in the order in which the files are in the file_list.txt file.
The result of the xargs cat command can then be piped yet again to the Linux tee command where I can then use redirection to write the ending result to a single output file as well as continue things on to the standard output as usual.
So the result off all of this is the text of file1.txt and file2.txt combined together as one and spit out to the console as well as the build.txt file. This might just be a silly string value, but in a real example not so different from this could be a build of many source code files into a single package file. I could pipe things threw some additional commands that might compact the source code into a minified rather than development form.