Newbie questions

72 views
Skip to first unread message

Jojy Varghese (jojvargh)

unread,
Nov 8, 2016, 4:57:37 PM11/8/16
to grp...@googlegroups.com
Hello Grpc group
We are considering gRPC for our messaging+rpc needs. Had a few questions that would help us proceed:

1. How is idempotency handled?
2. Is there de-duplication of requests on client side?
3. How do we hook concept of transaction?


Thanks in advance,
Jojy G Varghese








Carl Mastrangelo

unread,
Nov 21, 2016, 2:07:04 PM11/21/16
to grpc.io, jojv...@cisco.com
RPCs are not automatically retried currently, so there isn't a need to deduplicate.  In the (likely near) future, we will provide a way to mark an RPC as idempotent, which will allow the library to retry.  Note: if we can prove that the RPC never started (like a connection wasn't established), we will reconnect.

You can implement the concept of a transaction as a streaming RPC.  Just make each message of the stream some action, and on completion you can commit the transaction on the remote side.  That way if the RPC fails, the rest of the updates will not be applied.
Reply all
Reply to author
Forward
0 new messages