Should I use Capnp RPC or work with socket directly?

[andrewbanchich]

I'm using capnp for serialization already and will be using it for bidirectional communication over IPC via Unix domain socket.

The benefits the Capnp RPC system brings to me is really just:

1. Handle knowing size of request payload / when to stop reading bytes.
2. Handling the req / rep pattern (matching a response message ID with the ID of the request).

Are those two alone worth it to adopt Capnp RPC, or should my use case be fairly simple to do by working with the socket directly? I ask because I've read the RPC system and protocol is fairly complex, and I'm cautious of adopting it if I don't need its more complex features.

I haven't worked with sockets directly for very long so I may be underestimating some complexity there, but I'd guess the size of the message could just be a couple bytes at the beginning which are for the size of the payload to deserialize using capnp.