You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "Jun Gan (Jira)" <ji...@apache.org> on 2020/05/14 19:01:00 UTC

[jira] [Created] (SCB-1903) [Refactor service-registry Module] Refactor business logic when Consumer call Provider for the very first time

Jun Gan created SCB-1903:
----------------------------

             Summary: [Refactor service-registry Module] Refactor business logic when Consumer call Provider for the very first time
                 Key: SCB-1903
                 URL: https://issues.apache.org/jira/browse/SCB-1903
             Project: Apache ServiceComb
          Issue Type: Improvement
            Reporter: Jun Gan


Currently, the very first time when *consumer* calls *provider*, it creates *MicroserviceVersion* object by calling _g*etAggregatedRemoteMicroservice(serviceId)*_ method which interact with service center to retrieve microservice. {color:#FF0000}But{color} this call just retrieve basic informaiton instead of the schema content for the Microservice. Instead, it waits until ServiceRegistryListener.onCreateMicroserviceVersion is called to invoke SwaggerLoad to interact with service center again to retrieve the Provider's schema. 

 

Can we combine above two interactions with service center to ONE to improve the performance



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