grpcdotnetgo

module
v0.1.68 Latest Latest
Warning

This package is not in the latest version of its module.

Go to latest
Published: Sep 8, 2021 License: Apache-2.0

README

gRPC-dot-net-go

Contracts

It all starts with a proto file. In our case we want to have a custom server implementation that understands that the real downstream hanlder is in our DI. Fortunately we can use a protoc plugin to generate the GO code for that.

cd example
go get -u github.com/fluffy-bunny/protoc-gen-go-di/cmd/protoc-gen-go-di
protoc --go_out=. --go_opt=paths=source_relative --go-grpc_out=. --go-grpc_opt=paths=source_relative --go-di_out=. --go-di_opt=paths=source_relative internal\grpcContracts\helloworld\helloworld.proto

This will generate all the go files from our helloworld.proto

Make it looke like dotnet core

In dotnet core when a request comes in the DI has a concept of a scope. Here we do the same thing by creating that scoped container in a middleware

    requestContainer, _ := grpcdotnetgo.GetContainer().SubContainer()
		defer requestContainer.Delete()

		ctx = setRequestContainer(ctx, requestContainer)

		contextaccessor := contextaccessor.GetInternalGetContextAccessorFromContainer(requestContainer)
		contextaccessor.SetContext(ctx)

The middleware gets a SubContainer from the root container. When we use this new requestContainer to fetch objects from it, it will honor scoped services. The main root container will NOT give you an object that has been registered as scoped for good reason as the root container is global and is there for singletons.

Environment Variables

The frawework relies on the following environment variables, which can be overrided via cli arguements.

NAME Value Type Usage
APPLICATION_ENVIRONMENT String typeically used to load configs Appsettings.{APPLICATION_ENVIRONMENT}.yml
CLI Override

All environment variables can be override by the following cli argument and can be added multiple times. --env | -e

 go run .\cmd\server serve -e=GRPC_PORT=5105 -e=APPLICATION_ENVIRONMENT=Development -e=MYCONFIG__NESTED__MESSAGE=hello
Deep Nested Environment Variables

Deep nested Environment Variables are modeled after the Azure approach.

A__B__C=bird
A__B__SOMEMAP__dog__Weight=123  // where dog is map[string]interface{} and Weight is a key
A__B__SOMEARRAY__1__Weight=123  // where SOMEARRAY is []interface{} and contains a complex object that has Weight as a member variable.

Jump to

Keyboard shortcuts

? : This menu
/ : Search site
f or F : Jump to
y or Y : Canonical URL