When building a service in gRPC you define the message and service definition in a .proto file. gRPC generates client, server and DTO implementations automatically for you in multiple languages. At the end of this post you will understand how to make your gRPC API also accessible via HTTP JSON by using Envoy as a transcoding proxy. You can test it out yourself by running the Java code in the attached github repo. For a quick introduction on gRPC itself, please read gRPC as an alternative to REST.
Archive: November 2018
In Micronaut we can inject configuration properties in different ways into our beans. We can use for example the
@Value annotation using a string value with a placeholder for the configuration property name. If we don’t want to use a placeholder we can also use the
@Property annotation and set the
name attribute to the configuration property name. We have to pay attention to the format of the configuration property name we use. If we refer to a configuration property name using
@Property we must use lowercased and hyphen separated names (also known as kebab casing). Even if the name of the configuration property is camel cased in the configuration file. For example if we have a configuration property
sample.theAnswer in our
application.properties file, we must use the name
sample.the-answer to get the value.