<div dir="ltr">On 17 May 2016 at 22:31, Benoit Chesneau <span dir="ltr"><<a href="mailto:bchesneau@gmail.com" target="_blank">bchesneau@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="white-space:pre-wrap">nice! How does it compare to gen_rpc?<br></div></blockquote><div><br></div><div>Thank you. Similar aims (i.e. remove the problems caused by native RPC implementation). </div><div>- Tries to reduce the use of message passing. </div><div>- Supports pluggable transport protocols so that you can run erpc over TLS. </div><div>- SCTP support is on the roadmap. </div><div>- Supports load balancing across multiple nodes so the client doesn't need to care about trying multiple nodes in case one of the server nodes is down. Currently planning to add a consistent-hashing based load balancing but haven't quite decided on an API yet.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="white-space:pre-wrap"><br>When you say "It supports multiple TCP/TLS connections per host " does it means that we can multiple clients connected to the same node?<br></div></blockquote><div><br></div><div>Yes, with different names. That way each application can have its own dedicated connection(s) so that it doesn't suffer from sharing connections. For a single named connection, you can also have multiple transport connections. Also, connections are uni-directional so you have complete control over traffic flows.</div><div><br></div><div>cheers,</div><div>Chandru</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="white-space:pre-wrap"><span style="color:rgb(80,0,80)">On Tue, 17 May 2016 at 22:14, Chandru <</span><a href="mailto:chandrashekhar.mullaparthi@gmail.com" target="_blank">chandrashekhar.mullaparthi@gmail.com</a><span style="color:rgb(80,0,80)">> wrote:</span><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">I'm pleased to announce the first release of erpc. From the README<div> <br></div><div><div> This application is intended to be a replacement for native</div><div> RPC. It tries to mimic the native rpc API as far as possible. It</div><div> allows unidirectional connections between nodes. Where</div><div> bi-directional connections are required, they need to be</div><div> configured explicitly. There is host level and node level ACLs</div><div> configurable. It is possible to setup application specific</div><div> connections between nodes. It supports multiple TCP/TLS</div><div> connections per host and load balancing of traffic across nodes.</div></div><div><br></div><div>We haven't yet deployed this in production but it is giving us good results in load tests for some of our systems. We are releasing it early so that we can develop this in the open with community feedback and contributions.</div><div><br></div><div><a href="https://github.com/bet365/erpc" target="_blank">https://github.com/bet365/erpc</a><br></div><div><br></div><div>Many thanks to bet365 for open sourcing this.</div><div><br></div><div>cheers,</div><div>Chandru</div><div><br></div></div></div></div>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
</blockquote></div>
</blockquote></div><br></div></div>