https://github.com/jeffhollan/grpc-sample-node

Node application of a gRPC client and server, built for Azure Container Apps
https://github.com/jeffhollan/grpc-sample-node

azure azure-container-apps grpc

Last synced: 3 days ago
JSON representation

Node application of a gRPC client and server, built for Azure Container Apps

• Host: GitHub
• URL: https://github.com/jeffhollan/grpc-sample-node
• Owner: jeffhollan
• Created: 2021-11-24T22:01:08.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2021-11-25T16:39:07.000Z (about 3 years ago)
• Last Synced: 2025-01-23T00:45:09.686Z (4 days ago)
• Topics: azure, azure-container-apps, grpc
• Language: JavaScript
• Homepage:
• Size: 20.5 KB
• Stars: 1
• Watchers: 1
• Forks: 2
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# gRPC Sample : Node / JavaScript

### View this sample in other languages

| [C#](https://github.com/jeffhollan/grpc-sample-dotnet) | [Go](https://github.com/jeffhollan/grpc-sample-go) | [Java](https://github.com/jeffhollan/grpc-sample-java) | [JavaScript](https://github.com/jeffhollan/grpc-sample-node) | [Python](https://github.com/jeffhollan/grpc-sample-python) |

| ---  | --- | --- | --- | --- |

The following is a sample of a gRPC client calling another container running gRPC server to execute a `SayHello` call.  The solution runs on Azure Container Apps.

## Deploy the sample

### Azure CLI

```bash

RESOURCE_GROUP="grpc-sample"

LOCATION="canadacentral"

LOG_ANALYTICS_WORKSPACE="aca-logs"

ACA_ENVIRONMENT="aca-env"

az extension add -y \

  --source https://workerappscliextension.blob.core.windows.net/azure-cli-extension/containerapp-0.2.0-py2.py3-none-any.whl

az provider register --namespace Microsoft.Web

az group create \

  --name $RESOURCE_GROUP \

  --location "$LOCATION"

az monitor log-analytics workspace create \

  --resource-group $RESOURCE_GROUP \

  --workspace-name $LOG_ANALYTICS_WORKSPACE

LOG_ANALYTICS_WORKSPACE_CLIENT_ID=`az monitor log-analytics workspace show --query customerId -g $RESOURCE_GROUP -n $LOG_ANALYTICS_WORKSPACE --out tsv`

LOG_ANALYTICS_WORKSPACE_CLIENT_SECRET=`az monitor log-analytics workspace get-shared-keys --query primarySharedKey -g $RESOURCE_GROUP -n $LOG_ANALYTICS_WORKSPACE --out tsv`

# Create the Container Apps Environment

az containerapp env create \

  --name $ACA_ENVIRONMENT \

  --resource-group $RESOURCE_GROUP \

  --logs-workspace-id $LOG_ANALYTICS_WORKSPACE_CLIENT_ID \

  --logs-workspace-key $LOG_ANALYTICS_WORKSPACE_CLIENT_SECRET \

  --location "$LOCATION"

# Create the gRPC backend internal service

az containerapp create \

  --name grpc-backend \

  --resource-group $RESOURCE_GROUP \

  --environment $ACA_ENVIRONMENT \

  --image ghcr.io/jeffhollan/grpc-sample-node/grpc-backend:main \

  --ingress 'internal' \

  --target-port 50051 \

  --transport 'http2'

GRPC_SERVER_ADDRESS=$(az containerapp show \

  --resource-group $RESOURCE_GROUP \

  --name grpc-backend \

  --query configuration.ingress.fqdn -otsv)

# Create the HTTPS frontend gRPC client container

az containerapp create \

  --name https-frontend \

  --resource-group $RESOURCE_GROUP \

  --environment $ACA_ENVIRONMENT \

  --image ghcr.io/jeffhollan/grpc-sample-node/https-frontend:main \

  --environment-variables GRPC_SERVER_ADDRESS=$GRPC_SERVER_ADDRESS':443' \

  --target-port 8050 \

  --ingress 'external' \

  --query configuration.ingress.fqdn

```

### Try the solution

After deploying, get the FQDN of the https-frontend and browse to it. It will call the gRPC backend (via gRPC) and return a message to the client.