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

Liang He updated DUBBO-147:
---------------------------
    Labels: Dubbo gsoc2026  (was: gsoc2026)

> GSoC 2026 – Aligning Dubbo APIs with Modern gRPC APIs
> -----------------------------------------------------
>
>                 Key: DUBBO-147
>                 URL: https://issues.apache.org/jira/browse/DUBBO-147
>             Project: Apache Dubbo
>          Issue Type: Task
>            Reporter: Liang He
>            Priority: Major
>              Labels: Dubbo, gsoc2026
>
> h2. Background and Goal
> Apache Dubbo aims to provide full interoperability with the gRPC ecosystem 
> through the Triple protocol, which is designed to be fully compatible with 
> gRPC communication and tooling.
> However, the gRPC ecosystem has evolved significantly in recent years, 
> including improvements in APIs, streaming interfaces, and client/server 
> abstractions.
> Some of these updates have not yet been fully reflected in Dubbo's current 
> API design and SDK capabilities.
> This project aims to evaluate the latest gRPC APIs and align Dubbo’s APIs 
> with modern gRPC design patterns where appropriate.
> h2. Goal
> Expected tasks include:
>  # Investigate the latest gRPC API changes and features.
>  # Identify gaps between Dubbo’s APIs and the gRPC ecosystem.
>  # Improve or extend Dubbo APIs to better align with gRPC usage patterns.
>  # Improve interoperability between Dubbo services and gRPC clients.
>  # Provide examples and documentation for cross-framework usage.
> h2. Possible Extensions
>  * Improve gRPC streaming support
>  * Enhance proto-based service definitions
>  * Improve developer experience for cross-language services
> h2. Relevant Skills
>  * Java
>  * gRPC
>  * RPC frameworks
>  * Distributed systems
> h2. Potential Mentors
>  # Albumen Kevin, Apache Dubbo PMC, 
> [[email protected]|mailto:[email protected]]
>  # [email protected]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to