-
Notifications
You must be signed in to change notification settings - Fork 26.4k
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
[Feature] Dubbo Cloud Native : Add a mechanism to upgrade Dubbo services smoothly #4050
Milestone
Comments
mercyblitz
added a commit
to mercyblitz/dubbo
that referenced
this issue
Jun 4, 2019
…Dubbo services smoothly
mercyblitz
added a commit
to mercyblitz/dubbo
that referenced
this issue
Jun 4, 2019
mercyblitz
pushed a commit
that referenced
this issue
Jun 26, 2019
* Polish apache/incubator-dubbo/#4096 : To add new module for Dubbo Event * Polish #3942 : Dubbo Cloud Native: To Add Service registration and discovery abstract * Polish #3946 : Dubbo Cloud Native : To Add Dubbo metadata service * Polish #4093 : To add exported and unexported events for ServiceConfig * Polish #3984 : Add Service registration and discovery implementation for Zookeeper * Polish #4104 : To add initialized and destroyed events for ReferenceConfig * Polish #3946 : Refactor Dubbo metadata service * Polish #3946 : To Add MetadataServiceExporter into dubbo-config-api * Update ${project.parent.version} * Polish #3946 : Refactor Dubbo metadata service * Polish apache/incubator-dubbo/#4096 : Remove the duplicated word * Polish #4119 : DynamicConfiguration adds the publish and multiple get configuration methods * Polish #4120 : To add DynamicConfiguration implementation for Zookeeper * Polish #4121 : Add the mapping from service metadata to service name * Polish apache/incubator-dubbo/#3790 : Dependencies with no license * Polish #4071 : @reference can't match the local @service beans * Update version to be 2.7.3 * Polish #3946 : Add thread-safe and performance optimization * Polish #3946 : Add thread-safe and performance optimization * Polish #3946 : Add thread-safe and performance optimization * Update 2.7.3 * Polish #4104 : To add more events for dubbo-config-api * Polish #3942 : Dubbo Cloud Native: To Add Service registration and discovery abstract * Polish #3984 : Add Service registration and discovery implementation for Zookeeper * Add Bootstrap * Polish GA * Polish #4050 : Dubbo Cloud Native : Add a mechanism to upgrade Dubbo services smoothly * Polish #4093 : To add DubboServiceDestroyedEvent * Polish #4050 : Dubbo Cloud Native : Reactor * Polish #3946 : Remove SPI * Polish #4265 : [Feature] Dubbo Cloud Native - Add Bootstrap * Polish #4265 : [Feature] Dubbo Cloud Native - Add Bootstrap * Polish #4265 : Add test dependencies * Polish /#3942 : Refactor implementation * Polish #3984 : Refactor * Add Nacos implementation * Polish #3984 : Add Nacos implementation * Polish #4268 : Dubbo Event - To support Generic event type handle * Polish #4268 : Update JavaDoc * Polish #4268 : Add GenericEventListener implementation * add cache for MetadataServiceProxy * support multiple metadata and configcenter * unify metadata implementation * add missed files * remove duplicated files * add new SPIs and modules to dubbo-all pom.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Considering this scenario, there is a Dubbo service named
UserService
with two versions, one is a lower version running in the "app1" and another is higher deploying in a new release of "app1". These two versions are probably servicing for a long time, thus the clients have to subscribe to the two-versionedUserService
both.Suppose the
UserService
with the lower version is being replaced by the higher one, the client requires to be aware of the difference of these two-versionedUserService
, its metadata should be identified and present inMetadataService
.The text was updated successfully, but these errors were encountered: