Nacelle Base gRPC Process

Abstract gRPC server process for nacelle.

For a more full-featured gRPC server framework built on nacelle, see scarf.

Usage

The supplied server process is an abstract gRPC server whose behavior is determined by a supplied ServerInitializer interface. This interface has only an Init method that receives application config as well as the gRPC server instance, allowing server implementations to be registered before the server accepts clients. There is an example included in this repository.

The following options can be supplied to the server constructor to tune its behavior.

• WithTagModifiers registers the tag modifiers to be used when loading process configuration (see below). This can be used to change default hosts and ports, or prefix all target environment variables in the case where more than one gRPC server is registered per application (e.g. health server and application server, data plane and control plane server).
• WithServerOptions registers options to be supplied directly to the gRPC server constructor.

Configuration

The default process behavior can be configured by the following environment variables.

To use the server, initialize a process by passing a Server Initializer to the NewServer constructor. A server initializer is an object with an Init method that takes a nacelle config object (as all process initializer methods do) as well as a *grpc.Server. This hook is provided so that services can be registered to the gRPC server before it begins accepting clients.

The server initializer will have services injected and will receive the nacelle config object on initialization as if it were a process.

To get a better understanding of the full usage, see the example.

Configuration

The default process behavior can be configured by the following environment variables.

Using Multiple Servers

In order to run multiple gRPC servers, tag modifiers can be applied during config registration. For more details on how to do this, see the example.

Remember that multiple services can be registered to the same grpc.Server instance, so multiple processes may not even be necessary depending on your use case.