Closed robertroeser closed 5 years ago
Overall, I'm not 100% sold on this functionality.
RPC via protobuf IDL (existing functionality) seems like a huge win. Spring Boot handles the routing via annotated Java interfaces already. More complex apps should probably write this code themselves for a specific domain etc.
I'm not sure when I'd advise using this functionality...
Should this in theory be possible to integrate with Spring Boot's RPC mapping?
@yschimke it does not yet - but it RPC and the IPC stuff will work together if you used protobuf. The RPC code needs to support the composite metadata and routing frames (https://github.com/rsocket/rsocket/tree/master/Extensions) and then both will work with Spring messaging. There is a ticket to add the the extension frames into Javascript. Something similar needs to be implemented in JavaScript then so it can work with things like this / Spring Messaging.
If the performance is okay with the IPC stuff, then I think the code generator could generate IPC code under the covers. The main thing is the code generator creates a switch statement so need to do some testing of this vs a map - different types of map and see the difference that it ends up making.
@robertroeser Thanks. Regardless, as a secondary project this is great to see alternatives being explored. See which approaches are winning.
After all, I'm thinking the project should be renamed on rsocket-messaging
, etc
Provides IPC-style programming for those that don't want to use generated code.