You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by GitBox <gi...@apache.org> on 2022/11/10 13:32:18 UTC

[GitHub] [servicecomb-java-chassis] liubao68 commented on issue #3473: INFO Required: Edge gateway service routing to mesher Side car proxy

liubao68 commented on issue #3473:
URL: https://github.com/apache/servicecomb-java-chassis/issues/3473#issuecomment-1310287254

   A major difference of java chassis to other REST frameworks that if registers `swagger`  information to service center, and the client can parse the `swagger` information and do RPC invocation and service governance. 
   
   Make java chassis RPC run correctly, a microservice need to register swagger, and edge service is a special microservice. Without swagger, edge service can not parse the request and do a correct decoding and encoding. 
   
   If you have already used `Feign`, you can notice that java chassis RPC is quit simple than `Fegin`, no REST annotations needed. 
   
   Edge services most dispatchers can only forward requests to java chassis developed REST or HIGHWAY protocol services, they can automatic translate user REST requests to other protocols based on `swagger`. 
   
   If you need forward to other services do not have swagger registered, use `CommonHttpEdgeDispatcher` instead. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org