Rust and RPC at OkCupid

Re:Rust and RPC at OkCupid by tveita on Tuesday March 21, 2017 @07:38PM (#13927303)

> We use XDR - RFC 4506 and RPCv2 - RFC 1831 to communicate between our servers.

I see the appeal in using the same format everywhere, but it seems like they'd have a easier time using something with more mindshare, like Protocol Buffers, or even Thrift or Cap'n Proto.

All of those have Rust implementations, for instance, so you wouldn't have to implement your own parser.

[ Parent | on HN ]

Re:Rust and RPC at OkCupid by int_handler on Tuesday March 21, 2017 @08:46PM (#13927668)

Completely agree. I was wondering the same thing as I read this.

[ Parent | on HN ]

Re:Rust and RPC at OkCupid by vitno on Tuesday March 21, 2017 @11:09PM (#13928214)

OkCupid is over a decade old. XDR was pretty good back when people started writing our services.

My goal here isn't to migrate our RPC system... yet. My goal is to stand up Rust services in production. I need to be able to issue calls between services and thus, I need it to speak XDR. Migrating your RPC system in a production website is a non-trivial task.

I've done some investigation into switching to something like flatbuffers or cap'n proto. That's a project for another day though.

[ Parent | on HN ]

Re:Rust and RPC at OkCupid by int_handler on Tuesday March 28, 2017 @09:00PM (#13982367)

That makes sense. Thanks for explaining!

[ Parent | on HN ]