You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gsoc@community.apache.org by "Chaokun Yang (Jira)" <ji...@apache.org> on 2026/02/20 11:20:00 UTC

[jira] [Updated] (GSOC-322) Apache Fory Go & JavaScript gRPC integration

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

Chaokun Yang updated GSOC-322:
------------------------------
    Summary: Apache Fory Go & JavaScript gRPC integration  (was: Apache Fory Go and JavaScript gRPC integration)

> Apache Fory Go & JavaScript gRPC integration
> --------------------------------------------
>
>                 Key: GSOC-322
>                 URL: https://issues.apache.org/jira/browse/GSOC-322
>             Project: Comdev GSOC
>          Issue Type: New Feature
>            Reporter: Chaokun Yang
>            Priority: Major
>              Labels: fory, go, gsoc2026, javascript, mentor
>
> *Description:*
> Apache Fory can generate high-performance model code for Go and JavaScript/TypeScript from IDL, but end-to-end gRPC service binding generation across these two ecosystems is not yet complete as a unified workflow.
> This project will add Go and JavaScript/TypeScript gRPC code generation to the Fory compiler using Fory serialization instead of protobuf runtime payload types.
> The implementation should follow Fory compiler conventions, remain dependency-light in runtime layers, and prioritize low-overhead, performance-first behavior.
> *Potential Outcomes:*
> 1. Parse service IR and generate Go and JavaScript/TypeScript gRPC outputs for unary and streaming methods.
> 2. Generate Go outputs `*_service.go` and `*_grpc.go` with ServiceDesc, server interfaces, and client wrappers compatible with grpc-go.
> 3. Generate JavaScript/TypeScript service interface and gRPC binding outputs compatible with @grpc/grpc-js and existing JS/TS generator layout conventions.
> 4. Wire request/response payload handling through generated Fory serializer and deserializer functions in both targets.
> 5. Implement zero-copy deserialization buffer support for inbound gRPC payloads in both Go and JavaScript runtimes, with safe fallback paths when zero-copy cannot be applied.
> 6. Coordinate with JS/TS type generation so emitted message, enum, and union types are directly usable by generated gRPC stubs.
> 7. Add golden codegen tests for generated file names and key signatures for both language targets.
> 8. Add end-to-end interoperability tests between generated Go and JavaScript services, including Go server with JS client and JS server with Go client.
> 9. Add CI coverage for codegen tests, runtime codec tests, and Go<->JavaScript gRPC interoperability tests.
> 10. Provide runnable Go and JavaScript/TypeScript server-client examples using generated bindings and Fory codec.
> 11. Update compiler documentation for Go and JavaScript/TypeScript gRPC code generation usage and constraints.
> *Skills:*
> Go, JavaScript/TypeScript, Node.js, gRPC (grpc-go and @grpc/grpc-js), compiler/code generation, serialization internals, testing, performance optimization.
> *Difficulty:* 
> Medium to Hard
>  
> *Project size:* 
> 350 hours
> *Potential mentors:*
> Chaokun Yang, Weipeng Wang
> *Source links:*
> 1. https://github.com/apache/fory/issues/3274
> 2. https://github.com/apache/fory/issues/3278
> 3. https://github.com/apache/fory/issues/3280
> 4. https://fory.apache.org/docs/next/compiler/compiler_guide
> 5. https://github.com/apache/fory/tree/main/compiler
> 6. https://github.com/apache/fory/tree/main/go
> 7. https://github.com/apache/fory/tree/main/javascript
> 8. https://fory.apache.org/docs/guide/go/



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

---------------------------------------------------------------------
To unsubscribe, e-mail: gsoc-unsubscribe@community.apache.org
For additional commands, e-mail: gsoc-help@community.apache.org