Foreword
We started HashiCorp in 2012 to solve the challenges introduced by the rise of public cloud. The products we introduced were built in roughly the same order in which they’d be experienced by a new team building in the cloud. Vagrant was first, since creating a development environment was the first challenge we faced. Packer was second, to translate those development environments into cloud images. With the applications successfully deployed, the next challenge was networking between the multiple deployed images, and thus Consul was born.
The word microservice wasn’t used then, and the problem space was admittedly much smaller: we needed a way to find the address of a healthy instance of another application or service. The reality of cloud introduced several new technical challenges: global availability, automation friendliness, and the expectation that application instances came up and went down constantly. The initial release of Consul in 2014 solved all these challenges.
The beauty of new paradigms is that first-order challenges—once solved—give rise to second-order capabilities. The first-order challenge was service discovery in the world of public cloud. The second-order capability was then microservices, improved monitoring, more dynamic routing, and enhanced security by leveraging this new software-driven networking layer.
Consul was the natural place to enable these new capabilities, and over the years Consul has evolved to solve these difficult, modern networking ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access