The Consul architecture
Cloud-native applications require their workloads to be dynamically provisioned, so network modifications cannot be made manually for one service (say, the frontend) to connect to other services (say, the backend). The Consul architecture evolved differently compared to Kubernetes service discovery. Kubernetes uses iptables to point service IP addresses to the dynamic IP addresses of the pod, whereas Consul uses DNS for service discovery. Consul's service discovery can work with Kubernetes by injecting its DNS as an upstream server to the Kubernetes DNS. This architecture is mainly influenced by the modern gossip protocol, which works across multiple data centers.
The architecture of Consul supports loose coupling ...
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