In Unix systems, pipes and redirections are the bridges that join our programs. They are an underrated resource that can aid developers in their own work in powerful ways.
Today's post will explore pipes from their humble beginnings to how we use them in our programs (with example help from Golang).
Let's start with the humble pipe operator
|. If you are running a Unix shell, we can explore the pipe operator with some simple examples:
In this short example, we are echoing "Hello friends" and using a pipe to pass that output to the translate characters program
tr and taking all the lower case letters and upper casing them!
If you are unfamiliar with
man tr to see more. The description includes information on
In fact, we could add more pipes if we wanted to "glue" together more programs. We could even just do that with passing out put back to
You get the gist. What gets cool though is that you can create "named pipes" to start piping in some cooler ways.
What are "named pipes?". Let's define this with thanks again to our best friend Wikipedia:
In computing, a named pipe (also known as a FIFO for its behavior) is an extension to the traditional pipe concept on Unix and Unix-like systems, and is one of the methods of inter-process communication (IPC).
For clarification, FIFO in this context stands for "first-in, first-out". We now also understand that it is an extension on tradition pipes, so how do we make one? Luckily, we have a program
In terminal, we can run this and se that a named pipe will be created in the current working directory.
If were now to redirect anything to this named pipe ie
ls > example-pipe, the program will wait for something for the named pipe to pass to.
Example in current working directory
In another terminal, we can do that very things by running
cat < example-pipe to see the output in that terminal. Neat!
Getting output from the named pipe
Now, let's see how this can be applied to our programs. Here, I am going to use a Golang program to demonstrate how we can do this. I won't dive too deep into the code (Go has the amazing
go doc <search> feature to see information from the terminal) as this is simply a demo.
In the current working directory, create a
main.go file and add the following:
main function calls two functions:
SetupCloseHandlerthat creates a channel to listen out for our POSIX standard interrupt signal to exit the program.
ReadPipethat creates an infinite loop in the program to read from the "example-pipe" every 100ms.
SetupCloseHandler did not need to be public functions, I am just copying them across from other packages in my program that did require it to be so.
If we run
go run main.go in one terminal and
echo "test" > example-pipe into another, you can see that we get the output through the pipe in our Go program!
Output through Golang
Since we are indefinitely checking the pipe until the terminate signal is passed, we can run whatever we want into that
example-pipe and see it coming out through our program.
More README output
Of course, once we run our terminate signal, we can close the Go program (and you can see Go handling that signal).
Handling the terminate signal
Awesome! We've managed to create some named pipes and use content piped into them in our program!
This has been a short look at pipes and tying them into our programs. These become very useful when you are building tools to glue others together.
For example at work, we have a tool that I am about to take ownership of which connects together our developer experience from running our different services to migrations, installations and more. Named pipes is our way of being able to selectively pipe logs from each of those running services into one place to empower the developer experience and ensure that they are not overwhelmed!
I have linked a bunch of great resources below that relate to more information on both the pipes and everything that has been happening on the Golang side of things.
Image credit: Timothy L Brock