-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Why was Eureka 2.0 discontinued? #1129
Comments
Hi @ksurent. The open source work on eureka 2.0 (as embodied by the 2.x branch) is discontinued. The rationale for this is variously due to dependencies on some parallel open source projects that never came to full fruition, and also the big bang nature of the project. The majority of the motivations for eureka 2.0 is something that we (Netflix) still believe in, and have since realized internally. This is done in a much more evolutionary and incremental way, via variously:
|
Is this via non open sourced updates? or is this via configuration mentioned to in #1120 (comment) and introduced in #678 ? |
Thanks @qiangdavidliu and @mattnelson! Your insight is appreciated. Closing the ticket because my curiosity has been satisfied. |
@mattnelson the changes you referenced were indeed client side updates to help with client auto-discovery of the REST readonly cluster. The server side code for the read only servers (both REST and gRPC) are both internal at the moment unfortunately. |
@ksurent thank you for the information. |
Hi,
this is not a bug a report but a question. Having read motivations for Eureka 2.0 and Eureka 2.0 architecture overview, I started wondering why the work was discontinued. The ideas in the motivations document seem all reasonable and the architecture overview also makes sense.
I'm wondering if someone from Netflix or someone who is familiar with the situation can shed some light on this? Did you find any flaws in the design or difficulties in implementing it? Your insight would be much appreciated.
The text was updated successfully, but these errors were encountered: