search

jhipster / jhipster-registry

JHipster Registry, based on Spring Cloud Netflix Eureka and Spring Cloud Config
Apache License 2.0
698 stars 657 forks source link

future of jhipster-registery #584

Open gladiator009 opened 1 year ago

gladiator009 commented 1 year ago

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 commented 1 year ago

Any update on this?

pascalgrimaud commented 1 year ago

Hello @gladiator009

You can have a look at this ticket: https://github.com/jhipster/generator-jhipster/issues/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.