Summary

Well, I truly hope you enjoyed that chapter. We've seen how Consul is able to, in many real-world scenarios, scale to incredibly large numbers of nodes. We've seen how read replicas and, more importantly, the use of Autopilot enables us to scale our server clusters to support networks with tens of thousands of nodes. I believe I've even heard recently of a company running Consul in production with over 100,000 nodes! Centralizing the operation for all services on a system that large can be challenging for sure, so enabling namespaces not only helps scale the application usage within Consul but also the dependency on humans to operate the system as it grows. Finally, we've looked at federating our Consul clusters in a couple of ways to help span our service availability across data centers. As I've said since the beginning, Consul enables communication across components and services. Now those communication paths are no longer bound by scale or geography...