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/06/19 06:39:00 UTC
[jira] [Resolved] (SCB-1739) separate swagger registry and dicovery
from instance registry and discovery
[ https://issues.apache.org/jira/browse/SCB-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
liubao resolved SCB-1739.
-------------------------
Resolution: Fixed
see https://issues.apache.org/jira/browse/SCB-1933
> separate swagger registry and dicovery from instance registry and discovery
> ---------------------------------------------------------------------------
>
> Key: SCB-1739
> URL: https://issues.apache.org/jira/browse/SCB-1739
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Java-Chassis
> Reporter: liubao
> Assignee: liubao
> Priority: Major
> Fix For: java-chassis-2.1.0
>
>
> separate swagger registry and dicovery can done from following :
> # from service-center
> # from local archive(folder)
> # from local interface definition(now called 3rdparty invocation feature)
> # from other microserivces(first find instance, and than find it by query the instance )
>
> Design thinkings(DISCCUSS) :
> For instance registry and dicovery / schema registry and discovery, we can implement a composite pattern. Users can register a set of providers, and then for each provider to discover the informantion and merge the result.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)