Question on "Decentralized IPAM"
From what I understand DHCP and DNS are decentralized networking protocols. (They actually still require a hub (the DNS Server) but we’ll ignore that for now.)
Next generation IPAM claims to leverage DHCP and DNS but provide “centralized IP address management.” The way I think this works is that a centralized server holds the IP addressing schema and the address rules so that when an address (and the configuration on that address, i.e., TTL), is assigned an entry in the centralized DB is created which improves network ops. (No address conflicts, deterministic address assignment, centralized monitoring point, etc.)
The question is: What system is centralized IP management replacing? What was there before centralized IPAM?
Bonus related question (same flavor of “what was there before?”) –
One of the advantages of centralized IPAM is application/context aware traffic routing. For ex. You have data from a container swarm backing an application that all talks to a MongoDB backend. The network would make sure all the data from that container swarm is routed (directly?) to the Mongo backend.
The question is two parts (sorry).
1 – What was there before? Was data just being broadcast shotgun style to all the clients on the network?
And 2 – Even if data was just being broadcast, I don’t see where the efficiency gains are. If data was just being pushed out to every client on the network and now it’s being pushed to one particular client it still doesn’t increase the throughput of the applicable client. (It does increase the overall network bandwidth though since less packets are being transmitted to clients that won’t use the data. Is that where the performance improvement is?)
[link] [comments]
from IT https://ift.tt/34Y0K1Z
No comments: