Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

future of jhipster-registery #584

Open
gladiator009 opened this issue Oct 7, 2023 · 2 comments
Open

future of jhipster-registery #584

gladiator009 opened this issue Oct 7, 2023 · 2 comments

Comments

@gladiator009
Copy link

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.

@gladiator009
Copy link
Author

Any update on this?

@pascalgrimaud
Copy link
Member

Hello @gladiator009

You can have a look at this ticket: jhipster/generator-jhipster#19109

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants