Mechanical Advantage
Learn about the control plane, its role, and when it is needed along with its cost. Also learn about mechanical advantages and what happens when automation goes wrong.
Control plane
In the previous chapters we worked our way up from bare metal through layers of abstraction and virtualization to create a sea of instances running on machines. We’ve got software scattered around like an upended box of LEGO blocks. It’s up to the control plane to put these pieces in the right place and knit them together into a somewhat coherent whole.
The control plane encompasses all the software and services that run in the background to make production load successful. One way to think about it is this: if production user data passes through it, it’s production software. If its main job is to manage other software, it’s the control plane.
A challenge we’ll face in this chapter is that the solution space is not well partitioned among tools, packages, and vendors. It’s nowhere near as simple as picking one download from each column. There are overlaps and gaps. Not every combination will work together. No single package does everything. We are left with a lot of integration effort and plenty of trial and error.
Tiers of control
As we look at the control plane, keep in mind that every part of this is optional. We can do without every piece of it, if we’re willing to make some trade-offs. ...