You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@servicecomb.apache.org by "liubao (Jira)" <ji...@apache.org> on 2020/02/21 03:03:00 UTC

[jira] [Closed] (SCB-13) refactor service registry module

     [ https://issues.apache.org/jira/browse/SCB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

liubao closed SCB-13.
---------------------
    Resolution: Duplicate

> refactor service registry module
> --------------------------------
>
>                 Key: SCB-13
>                 URL: https://issues.apache.org/jira/browse/SCB-13
>             Project: Apache ServiceComb
>          Issue Type: Improvement
>          Components: Java-Chassis
>            Reporter: Eric Lee
>            Priority: Major
>              Labels: roadmap, service-orchestration
>
> Currently, the service registry module in Java Chassis has the following problems:
> - Low level components access high level components frequently. The cyclic relationships make the implementation complicated and introduce some redundant access points.
> - Low level components should be stateless to be reused by high level components. Introducing state into low level components makes it relies heavily on the high level components, causing cyclic relationships.
> - Hard to integrate with third-party framework. It does not provide a standalone client with cache capability inside. It also requires the configurations should be loaded from dynamic properties.
> Details: [http://servicecomb.io/docs/service-registry-refactor-proposal/|http://servicecomb.io/docs/service-registry-refactor-proposal/]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)