We have a spring boot microservice project generated by jhipster. Jhipster built integrated consul for us, and we haven't really touched it since then. We are moving to a new deployment with RedShift, which should handle service discovery and other tasks which consul was doing, but all of our services are still dependent on consul.
Is it possible for consul and redshift to play nice? Does one interfere with the other? It seems to me that consul would bottleneck all traffic, but I can't find any sources suggesting that they are competing techs. If there is a conflict, can we refactor the consul integration to work with redshift instead?
Are you talking about AWS Redshift or Red Hat Openshift ? If it is the former I don't see the connection with Consul as it is a managed Database that can be a replacement for MySQL/Postgres, etc.
However for Openshift, it is running Kubernetes under the hood, which is nice as our Kubernetes sub-generator already supports consul microservices and can even help you deploy an HA Consul registry in a statefulset. An alternative to this consists in switching out consul discovery with Spring Cloud Kubernetes however this break discovery features in development.