SAService ArchitectDocumentation

/

Data connectorsgRPC

Data connector gRPC

gRPC connector

gRPC server or client transport with generated contract bindings.

When to use

Configure this object once per external system or listener. Add concrete routes, methods, topics or schedules as endpoints inside it.

Behavior

Owns transport-level connection and implementation settings.
Can contain multiple endpoints.
Input and Sink streams reference endpoints, not the connector directly.

General properties

Connector identity and language-specific runtime adapters

PropertyTypeDescription

namestring

Connector name used in the designer and generated symbols.

Required

typeDataConnectorType

External system kind. It is locked after endpoints are created.

RequiredAllowed: HTTP, gRPC, Kafka, Custom, Cron, Temporal

goImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: google/grpc

cppUserverImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: userver/grpc

cppBoostImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: asio/grpc

pythonImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: google/grpc

rustImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: rust/tonic

typeScriptImplementationimplementation

Runtime adapter selected for this target language.

RequiredAllowed: grpc/grpc-js

gRPC properties

gRPC-specific connection settings

PropertyTypeDescription

moduleModule

Module containing generated protobuf types.

Required

addressURI

Client connection address.

Default: dns:///localhost:50051

connectionsCount1..1000

Independent sink connections distributed by the adapter.

Default: 1

Configuration example

type: gRPC
module: orders_api
address: dns:///orders:50051