Deploying Applications on Apache Dubbo

Deploying Istio Environment

Mon, 01 Jan 0001 00:00:00 +0000

1. Preparation

Docker, Helm, and kubectl environments are installed.
Dubbo-go CLI tools and dependencies are installed.

2. Deploy Istio Environment

Install the Istio base CRD and istiod components using Helm. You can also refer to the Istio Documentation for installation using istioctl.

$ helm repo add istio https://istio-release.storage.googleapis.com/charts
$ kubectl create namespace istio-system
$ helm install istio-base istio/base -n istio-system
$ helm install istiod istio/istiod --namespace istio-system

Delete the Istio horizontal pod autoscaler resources

Deploying Dubbo-go application in Istio environment

Mon, 01 Jan 0001 00:00:00 +0000

In this chapter, we will quickly create a set of Dubbo-go Server and Client applications using the application template and deploy them in an Istio cluster; observe, debug, and verify service discovery and successful calls.

The matching mesh sample is available at dubbo-go-samples/mesh.

1. Preparation

dubbogo-cli and related dependency tools are installed. Install dubbogo-cli from tools/dubbogo-cli in the dubbo-go repository. grpc_cli is optional for local debugging.
The docker, helm, and kubectl environments are installed. (Arm machines must support docker buildx)
The task Deployment of Istio Environment is complete.

2. Developing the Server-side Dubbo-go Application

2.1 Create Project Template with dubbogo-cli

$ mkdir mesh-app-server
$ cd mesh-app-server
$ dubbogo-cli newApp . 
$ tree .
.
├── Makefile
├── api
│ └── api.proto
├── build
│ └── Dockerfile
├── chart
│ ├── app
│ │ ├── Chart.yaml
│ │ ├── templates
│ │ │ ├── _helpers.tpl
│ │ │ ├── deployment.yaml
│ │ │ ├── service.yaml
│ │ │ └── serviceaccount.yaml
│ │ └── values.yaml
│ └── nacos_env
│ ├── Chart.yaml
│ ├── templates
│ │ ├── _helpers.tpl
│ │ ├── deployment.yaml
│ │ └── service.yaml
│ └── values.yaml
├── cmd
│ └── app.go
├── conf
│ └── dubbogo.yaml
├── go.mod
├── go.sum
└── pkg
 └── service
 └── service.go

dubbogo-cli is maintained in the dubbo-go repository under tools/dubbogo-cli, and the generated template is the starting point for the rest of this guide.

Traffic Management

Mon, 01 Jan 0001 00:00:00 +0000

In this section, we will continue from the previous task 【Deploying Dubbo-go Applications in Istio Environment】.

In the previous task, we deployed a set of Dubbo-go Server and Client applications in the cluster and verified that service discovery and invocation were successful. In this section, we will create a new version of the server application. By configuring VirtualService and DestinationRule, we will achieve routing management and traffic shifting capabilities.

The matching traffic-management manifests are available at dubbo-go-samples/mesh/deploy/traffic.

Graceful Shutdown

Mon, 01 Jan 0001 00:00:00 +0000

Graceful Shutdown

Sample source: dubbo-go-samples/graceful_shutdown.

1. Background

During version releases, scaling, or node migration, Kubernetes, systemd, or an operations platform stops old instances and starts new ones. If an old instance exits immediately, the registry, client-side invoker cache, and upstream traffic may be briefly inconsistent: the registry may not have propagated the delete event, and upstream requests may still be running. For high-traffic services, this can cause connection resets, request failures, timeout retries, and alert storms.

Proxyless Service Mesh

Mon, 01 Jan 0001 00:00:00 +0000

Sample source: dubbo-go-samples/mesh.

1. What is Proxyless Service-Mesh?

1.1 Brief Analysis of Service Mesh

Istio is the most popular open-source service mesh today. It consists of a control plane and a data plane, as shown in the architecture below, image sourced from istio official website

The control plane located at the bottom half of the image is responsible for the distribution of resources like configurations, service information, and certificates. The data plane, located at the upper half, focuses on the communication traffic between services; traditional service meshes intercept all business network traffic through proxies, which need to be aware of the configuration resources issued by the control plane to manage traffic directions as required.