refactor(getty): remove legacy config dependency from remoting/getty (#3401) * refactor(getty): remove legacy config dependency from remoting/getty Replace all config.Get*() calls in initClient and initServer with URL attribute reads, following the pattern already used by triple/grpc/dubbo3 protocols. The URL attributes (ProtocolConfigKey, TLSConfigKey, ApplicationKey) are already populated by callers in server/action.go and client/action.go, so the legacy config fallback path is redundant. Changes: - getty_client.go: replace config.GetApplicationConfig() / config.GetRootConfig().Protocols / config.GetRootConfig().TLSConfig with url.GetAttribute() reads. Collapse two redundant TLS blocks into one, fixing a copy-paste bug where srvConf was used instead of clientConf. Add IsClientTLSValid validation that was missing in the legacy TLS path. - getty_server.go: same config → URL attribute migration. - Imports: remove dubbo.apache.org/dubbo-go/v3/config and dubbo.apache.org/dubbo-go/v3, add common/config for EnsureApplicationAttribute. - Update stale comments referencing rootConfig. * refactor(getty): simplify protocol guard by removing ineffective GetParam check The protocol name is stored in url.Protocol field, not in URL params. GetParam(constant.ProtocolKey) always returns empty string in normal flow, making the outer condition a no-op. Replace the nested check with a direct url.GetAttribute(ProtocolConfigKey) guard. * refactor(getty): merge redundant protocol guard and retrieval The guard and the subsequent GetAttribute call both read the same ProtocolConfigKey attribute. Since the guard already verified existence and returned on miss, the second GetAttribute's !ok branch was dead code. Merge into a single read block. * refactor(getty): merge type assertion and TLS validity check into single if statement * fix(getty): fail-secure on TLSConfigKey type assertion failure When TLSConfigKey is present but not of type *global.TLSConfig, log an error and return instead of silently skipping TLS initialization. This prevents misconfigured TLS from being silently downgraded to plaintext — consistent with how other protocols (gRPC, triple) handle the same scenario. Also add TestInitClientTLS and TestInitServerTLS to cover: - valid TLS config → SSLEnabled/TLSBuilder set - invalid TLS config → TLS remains disabled - wrong TLSConfigKey type → error logged, early return
English | 中文
Apache Dubbo-go is a high-performance RPC and microservice framework compatible with other Dubbo language implementations. It leverages Golang's concurrency features to provide efficient service governance, including service discovery, load balancing, and traffic management. Dubbo-go supports multiple protocols, such as Dubbo, JSONRPC, Triple(gRPC-compatible), gRPC, HTTP, HTTP2, and HTTP/3 (experimental), ensuring seamless integration in heterogeneous environments.
You can visit the official website for more information.
For detailed changes, refer to CHANGELOG.md.
3.3.1: Optimized configuration hot-reloading with content-based caching to prevent redundant notifications. Added experimental HTTP/3 support, Apollo integration, and Triple protocol OpenAPI generation. Fixed critical race conditions in service discovery under high-concurrency.
3.3.0: Introduced script routing, multi-destination conditional routing, Triple protocol keepalive and connection pooling, Nacos multi-category subscriptions, and enhancements for observability and interoperability.
To install Dubbo-go, use the following command:
go get dubbo.apache.org/dubbo-go/v3@latest
You can learn how to develop a dubbo-go RPC application step by step in 5 minutes by following our Quick Start demo.
It's as simple as the code shown below, you define a service with Protobuf, provide your own service implementation, register it to a server, and start the server.
func (srv *GreetTripleServer) Greet(ctx context.Context, req *greet.GreetRequest) (*greet.GreetResponse, error) {
resp := &greet.GreetResponse{Greeting: req.Name}
return resp, nil
}
func main() {
srv, _ := server.NewServer(
server.WithServerProtocol(
protocol.WithPort(20000),
protocol.WithTriple(),
),
)
_ := greet.RegisterGreetServiceHandler(srv, &GreetTripleServer{})
if err := srv.Serve(); err != nil {
logger.Error(err)
}
}
After the server is up and running, call your service via cURL:
curl \ --header "Content-Type: application/json" \ --data '{"name": "Dubbo"}' \ http://localhost:20000/greet.GreetService/Greet
Or, you can start a standard dubbo-go client to call the service:
func main() {
cli, _ := client.NewClient(
client.WithClientURL("127.0.0.1:20000"),
)
svc, _ := greet.NewGreetService(cli)
resp, _ := svc.Greet(context.Background(), &greet.GreetRequest{Name: "hello world"})
logger.Infof("Greet response: %s", resp.Greeting)
}
See the samples for detailed information on usage. Next, learn how to deploy, monitor and manage the traffic of your dubbo-go application by visiting the official website.
Dubbo-go provides robust service governance capabilities:
The tools/ directory and the dubbogo/tools repository provide several utilities to streamline your Dubbo-Go development experience.
A tool that provides JSON Schema for Dubbo-Go configuration files, enabling editor assistance such as completion, hints, and validation.
For usage details, see the dubbo-go-schema README.
A command-line tool for bootstrapping, managing, and debugging Dubbo-Go applications.
A protoc plugin that generates Go client and server code for the Triple protocol from .proto definition files.
Note: This tool replaces the deprecated protoc-gen-dubbo3grpc and deprecated protoc-gen-go-triple.
For usage details, see the protoc-gen-go-triple README.
A formatting tool for Dubbo-Go developers that organizes Go import blocks according to the community style guide.
For usage details, see the imports-formatter README.
A warning-only scanner that detects exported variadic RPC contracts and prints migration guidance for cross-language scenarios.
Run make rpc-contract-check to use it locally.
Contributions, issues, and discussions are welcome. Please visit CONTRIBUTING for details on submitting patches and the contribution workflow.
Join our discussion group through Ding talk or WeChat.
If you are using apache/dubbo-go and think that it helps you or want to contribute code for Dubbo-go, please add your company to the user list to let us know your needs.
Apache Dubbo-go software is licensed under the Apache License Version 2.0. See the LICENSE file for details.