> Consul - EVERYONE should use service discovery, cloud or not.
Discovery means that you don’t know your service name? Or endpoints? How can one lose his service? Im def missing something :)
Discovery means that you don’t know your service name? Or endpoints? How can one lose his service? Im def missing something :)
When you do a rolling upgrade, a new service must be assigned to an available port different to the existing one. After starting you'll probably run some health checks, and once satisfied you'll want to switch traffic over to the new instance and halt the old. How do you tell the rest of your infrastructure what the new port is? Service discovery.
Rolling is trickier, but still, native cloud solutions do not use service discovery, imho.
Service discovery is in part DNS with low ttl, but there’s a part of it that ties in to configuration management, monitoring and observability as well.
If you “update dns” that means you’re doing a part of what consul does (only f ex nomad does it for you). Nothing magic, but you still “need it”.
Tags and metadata is a large part of it though, as well as configuring things automatically based on state of the SD and K/V.
In the end - whatever works, I guess.