Dubbo came alive this year and was accepted by Apache. Meanwhile, unfortunately, the Netflix Eureka component project under Spring Cloud has been announced as closed source.
Those of you who have migrated from Dubbo to Spring Cloud, are you ok?
Closed source: https://github.com/Netflix/eureka/wiki
The open source work on Eureka 2.0 has been stopped, relying on projects or related code from the Eureka 2.x branch of the open source library, at your own risk.
What is Eureka?
Developers using Spring Cloud as a microservices framework should know that Eureka is their default and recommended service registry component.
Eureka is first proposed as a service registry component because Netflix’s excellent suite, such as Zuul (Service gateway component) and Hystrix (fuse component), are Spring Cloud one-stop solutions.
Let’s look at the diagram of Eureka and service registration.
Eureka open source history
Netflix made Euerka open source in 2012.
The latest version of Eureka 1.x, version 1.9.3, will be the last open source version of Eureka.
There is no statement on the official website of Closed Source this time. We will continue to follow up whether there is a reversal of history or other conspiracies.
Where does Spring Cloud go?
Where will Spring Cloud go with Eureka’s closed source? Will the default service registry component be replaced later? I don’t know, Spring Cloud releases are coming out so fast that I can’t keep up.
Eureka 2.x has not been officially released yet, and Spring Cloud is developed on 1.x. The latest version relies on 1.9.2, so although most companies in China are using Eureka, it will not be affected for the time being.
1. X is relatively stable. Do not blindly upgrade or switch to other middleware. However, with Eureka’s closed source, it will be necessary to migrate to Consul, ZooKeeper, Etcd and other open source middleware.
What do you think of Eureka’s closed source and its impact? Welcome to comment.
Spring Boot & Cloud
Scan our wechat public number, dry goods updated every day.
