tl;dr: I'm not sure WF is the right place for GRPC integration
io.grpc: grpc-core grpc-protobuf grpc-stub with deps take 6.1 MB (using version 1.5.0)
2) speed of development
version 1.5.0 in July
version 1.8.0 in November
speed itself is not the main problem, point 3) is more concerning
3) changes in minor releases
I tried mvn clean package -Dgrpc.version=1.8.0 on undertow-grpc and got compilation
failure with 18 errors
Every minor (looked at 1.5.0+) has one of the following mentioned in
my impression is that direct support in OpenShift or
SWARM-627 would make sense.
5) yet another integration/rpc solution
We have Corba / EJB, JAX-WS, JAX-RS, JMS.
Do we want / need it grpc in WF? What would be the advantage of this integration?
I know I sound to pessimistic, feel free to turn me into grpc-optimist ;)
----- Original Message -----
On 12 December 2017 at 22:24, Stuart Douglas
> Not without writing a new protobuf compiler, the compiler does not provide
> any places to hook into the registration process, the only way I could
> manage to do it was to subclass the generated class with a proxy. Protobuf
> generates a fair bit of code for each class anyway, so I don't think the
> proxy will add much percentage wise.
The Google tooling for ProtoBuf expect you to use code generation
depending on the schema, but it's not the only toolset available.
Infinispan also uses ProtoBuf for encoding of client/server data yet
forcing people to use code generation seemed too annoying, so they use
In turn this is based on Square's Protoparser. I have no idea if it's
more efficient, but it's possible as the alternative feels less
verbose than the codegeneration approach; it's certainly more
Hibernate OGM has a "dialect" able to encode JPA storage operations
into Infinispan Remote calls using a combination of the above
libraries; in terms of usage people just deploy JPA annotated pojos on
WildFly and the necessary infrastructure is generated via an internal
metamodel and a chain of method references: no proxies nor code
> On Wed, Dec 13, 2017 at 1:30 AM, Andrig Miller <anmiller(a)redhat.com> wrote:
>> Because I have memory footprint on the brain, pretty much all the
>> time now, I wonder if you can change your approach in a way that would
>> lessen MetaSpace usage. MetaSpace usage is usually the second largest
>> memory hog in Wildfly/EAP, and under certain circumstances it can be
>> than heap, when the right JVM settings are used to control heap usage
>> of my presentation in 30 minutes).
>> On Tue, Dec 12, 2017 at 3:48 AM, Darran Lofthouse
>> <darran.lofthouse(a)jboss.com> wrote:
>>> On the security question, if we are interested in pursuing this we will
>>> get an analysis document started to look at the options we have for
>>> integration with our security implementation.
>>> Darran Lofthouse.
>>> On Mon, 11 Dec 2017 at 05:17 Stuart Douglas
>>>> Hi everyone,
>>>> I have done up a proof of concept of GRPC support in Wildfly, which can
>>>> be found at . GRPC is an RPC protocol designed by Google, that
>>>> easy cross platform invocations.
>>>> My proof of concept uses an Undertow based port of GRPC  and
>>>> basically works as follows:
>>>> - At deployment time Jandex is used to find all non-abstract classes
>>>> that implement io.grpc.BindableService
>>>> - I scan the class hierarchy of these classes to find the protobuf
>>>> generated base class, and create a subclass of this class using
>>>> ProxyFactory, overriding every method except bindService().
>>>> - An instance/proxy is created using the ComponentRegistry to do the
>>>> creation, and the generated proxy delegates all incoming calls to this
>>>> - At runtime any incoming HTTP/2 requests with a type of
>>>> application/grpc are intercepted, and passed through this newly created
>>>> Basically this means that all you need to do as an application
>>>> is define your GRPC endpoints using protobuf, implement the classes
>>>> generated by the protobuf compiler and then include them in your
>>>> application, and Wildfly will do the rest. CDI and EJB annotations on
>>>> GRPC services should work as normal, for example if you put @Stateless
>>>> on an
>>>> endpoint it should work as expected with a SFSB handling all
>>>> Note that this is a very early stage POC, and lots of stuff is missing
>>>> (most notably security).
>>>> Before I go to much further though I though that I should get some
>>>> feedback, e.g.
>>>> - Do we actually want this? I am not sure how much interest there is,
>>>> but it seems like GRPC could be very useful in a polyglot microservice
>>>> - Is the current implementation the best way of actually registering
>>>> GRPC services, or should we require some kind of defining annotation
>>>> - What security mechanisms should we support? Out of the box standard
>>>> GRPC is fairly limited
>>>> - What do we do about transactions? I am leaning towards not supporting
>>>> them over GRPC, as we already have solutions for Java invocation in the
>>>> of our EJB protocol, and I think non-Java clients are unlikely to want
>>>> use this.
>>>>  https://github.com/stuartwdouglas/wildfly/tree/grpc
>>>>  https://github.com/stuartwdouglas/undertow-grpc
>>>> wildfly-dev mailing list
>>> wildfly-dev mailing list
>> Andrig (Andy) T. Miller
>> Global Platform Director, Middleware
>> Red Hat, Inc.
> wildfly-dev mailing list
wildfly-dev mailing list