In the EJB 1.1 Specification, Sun Microsystem in according to OMG integrate RMI over
CORBA IIOP(Standard deFacto and more use in the years 80/90).
Most corba client invoke Ejb method from c++, ada etc by Corba Client.
Why not reproduce same scenario for HTTP2/gRPC herea?
Http2 has more fearture like Corba TCP Connection(Single Connection,Multiplezing, priority).
The good base of RMI-IIOP based to OMG Corba(IDL+IIOP/GIOP Message) have most power.
gRPC promote an rpc over http2(only efficient alternative for REST JSON+HTTP), but
there are more work for developer.
-
generate proto interface(on java there is java interface by OMG IDL ),
-
generate and populate stub code(on Ejb this is gratis with Runtime Stub Generation/Downloading feature).
-
generate and populate skeleton code(on Ejb this is gratis with Runtime Skeleton Generation feature).
-
for a server-to-server communication is a good choice ejb-to-ejb communication, and support distributed transaction managed by conintainer.
-
The EJB CMT Feature (EJB container managed transaction inbound outbound) is power feature.
An interesting project is jakarta-RPC but in this moment is very distance from Remote
EJB.