cnzakii opened a new issue, #16595:
URL: https://github.com/apache/dubbo/issues/16595

   ### Pre-check
   
   - [x] I am sure that all the content I provide is in English.
   
   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no 
similar feature requirement.
   
   ### Apache Dubbo Component
   
   Python SDK (apache/dubbo-python)
   
   ### Descriptions
   
   The current Dubbo Python supports a small part of Dubbo: it serves and calls 
Triple, registers interfaces on ZooKeeper, and offers random and CPU load 
balancing. Interoperating with the rest of the Dubbo ecosystem also needs the 
Dubbo protocol with Hessian 2, Nacos, application-level service discovery and 
the governance of the other Dubbo languages, which reach every layer of the 
current code: the call model, configuration and lifecycles. This issue proposes 
rebuilding Dubbo Python as a Python-native framework that covers them.
   
   Scope:
   
   - Triple, interoperable with gRPC, and the Dubbo protocol with Hessian 2, 
both with TLS.
   - Application-level and interface-level service discovery on ZooKeeper and 
Nacos, metadata and configuration centers.
   - Load balancing, cluster fault tolerance, routing rules, dynamic 
configuration and filters.
   - Services as `typing.Protocol` with async calls, on asyncio with AnyIO, for 
Python 3.11 to 3.14.
   
   Compatibility:
   
   - The public API is new, so code written for earlier releases needs to be 
ported.
   - Wire formats and registry entries follow Dubbo Java and Dubbo Go.
   
   Pull request: apache/dubbo-python#53
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a pull request to fix on your own?
   
   - [x] Yes I am willing to submit a pull request on my own!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to