You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see the generator of v8 doesn't ask for options of Service Discovery for monolith generation and it recommends Consul for micro-service generation.
Please advise if there are any plans to retire jhipster-registry in the future, as it will have significant impact on our projects that are using this registry. Do we have to plan to migrate to consul?
If the plan is to retire jhipster-registry, how much time do we have before the support is withdrawn.
The text was updated successfully, but these errors were encountered:
As said, it's because the Netflix stack which is not maintained anymore. That's the reason why Consul is the default option in generator-jhipster v8.
About JHipster Registry, it will stay like this. The project will stay Open Sourced, and won't be deleted.
If someone wants to maintain, improve it, he/she will be welcome.
I see the generator of v8 doesn't ask for options of Service Discovery for monolith generation and it recommends Consul for micro-service generation.
Please advise if there are any plans to retire jhipster-registry in the future, as it will have significant impact on our projects that are using this registry. Do we have to plan to migrate to consul?
If the plan is to retire jhipster-registry, how much time do we have before the support is withdrawn.
The text was updated successfully, but these errors were encountered: