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

Sync with JHipster 7.1.0 #502

Closed juliensadaoui closed 3 years ago

juliensadaoui commented 3 years ago
Overview of the issue

I open this ticket to sync the registry with jhipster 7.1.0 and remove the administrative server Below, please find a list of major changes.

Motivation for or Use Case

The JHipster Registry is composed of a Eureka Server, that provides as a discovery server for application. It is also an administration server, with dashboards to monitor and manage applications. The Registry is an application type gateway because it manages applications using Netflix Zuul.

JHipster v7 uses Spring Cloud Gateway instead of Netflix Zuul as gateway component. Spring Cloud Gateway is based on the reactive stack and we must migrate the registry on the Webflux module. However, Eureka Server requires a Servlet container. Both Eureka server and Spring Cloud Gateway can't work together. Spring Cloud no longer supports Netflix Zuul.

I suggest removing the administrative server in the Registry. This functionality is proposed by the JHipster Control Center. The JHipster Registry will keep two main purposes:

juliensadaoui commented 3 years ago

I started to work on the upgrade to JHipster v7. https://github.com/juliensadaoui/jhipster-registry/tree/jhipster-7

juliensadaoui commented 3 years ago

Merged in the main branch. See #503

juliensadaoui commented 3 years ago

Bounty claimed at https://opencollective.com/generator-jhipster/expenses/45936