A couple of weeks ago, I saw a demo of Waypoint, the new tool Hashicorp announced today, that aims to provide an easy, intuitive and customizable “build, deploy and release” workflow.
This post isn’t a tutorial or a guide on how to use the product; the official documentation and tutorials are a good resource to understand how to configure and use the tool. In this post, I explain why I believe that philosophically, the design of Waypoint holds a lot of promise and potential.
It probably helps to begin this post by spelling out what Waypoint isn’t.
Waypoint is not:
A bash script is commonly a set of commands. There are three standard file descriptors of any command:
There are two commonly used redirection operators:
The most basic example of redirecting the output of a command to a file is:
echo "hello world" 1> foo.txt
This redirects the output of the echo command to a file called
Yesterday, I read a phenomenal paper on how disruption free release of services that speak different protocols and serve different types of requests (long lived TCP/UDP sessions, requests involving huge chunks of data etc.) works at Facebook.
One of the techniques used by Facebook is what they call “Socket Takeover”.
Socket Takeover enables Zero Downtime Restarts for Proxygen by spinning up an updated instance in parallel that takes over the listening sockets, whereas the old instance goes into graceful draining phase. …