Why Consul (Service Registry) added in vConnect 2.0. How it will differed from Eureka?
I am not at right place to answer this but I think it had something to do with HA in Eureka at that time.
@naks Could you please answer this?
Multiple aspects to add Consul in Vahana 2.0
=> High Availability
=> Centralized configuration (Application properties or YML ) in a single place.
=> Vault usage for future to secure credentials
=> Hot reload of application properties without microservice restart like settings of timeout etc
As per my understanding all the above can be also done in Spring Could and Eureka.
High Availability : Using Eureka Server Cluster
Centralized configuration: By Using Spring Cloud Config Server.
Vault usage : By using spring cloud vault config
Reload of application: Not Direct but can be also done.