this looks really sweet. i've never understood why gRPC limits itself to protobufs only when the protobufs have a canonical json representation. i'm glad that twirp is fixing that piece.
You can use gRPC with FlatBuffers, too.
Twirp: A new RPC framework for Go
11–20 of 99 posts
Re: Twirp: A new RPC framework for Go
#12Hey everyone! I'm the OP and primary author of Twirp. I'm happy to answer any questions and hear feedback.
You can also reach me directly, if you like, email is in my profile.
Re: Twirp: A new RPC framework for Go
#13Hey everyone! I'm the OP and primary author of Twirp. I'm happy to answer any questions and hear feedback. You can also reach me directly, if you like, email is in my profile.
Thanks for posting! Does Twirp use a single HTTP request per call, or does it use a persistent connection similar to the net/rpc package? If the latter, does it provide options for heartbeat, reconnect and retry?
EDIT: the blog post covers this in the protocol section. Every request is a POST :)
Re: Twirp: A new RPC framework for Go
#14Looks like the website got a HN hug of death and isn't really loading for me whatsoever.
Re: Twirp: A new RPC framework for Go
#15Looks like the website got a HN hug of death and isn't really loading for me whatsoever.
Unlikely? It's hosted on medium - I'm pretty sure they can handle the load. However here is the cached version: https://webcache.googleusercontent.com/search?q=cache:6vYOM9...
Re: Twirp: A new RPC framework for Go
#16Looks like the website got a HN hug of death and isn't really loading for me whatsoever.
Must just be your network. I would be surprised if HN traffic could bring down Medium
Re: Twirp: A new RPC framework for Go
#17Hey everyone! I'm the OP and primary author of Twirp. I'm happy to answer any questions and hear feedback. You can also reach me directly, if you like, email is in my profile.
Thanks for posting! How did you work around issues with GRPC on AWS/ELB?
Re: Twirp: A new RPC framework for Go
#18Really excited about this. I didn't like how opaque and heavy gRPC is. Also I really wanted support for JSON. Mostly for these reasons, RCP hasn't been implemented in my architecture yet (Just using standard REST)
Twirp is everything I wanted in an RPC framework and I'm looking forward to implementing it ASAP. Thanks Twitch team :)
Re: Twirp: A new RPC framework for Go
#19Hey everyone! I'm the OP and primary author of Twirp. I'm happy to answer any questions and hear feedback. You can also reach me directly, if you like, email is in my profile.
Thanks for posting! Does Twirp use a single HTTP request per call, or does it use a persistent connection similar to the net/rpc package? If the latter, does it provide options for heartbeat, reconnect and retry? EDIT: the blog post covers this in the protocol section. Every request is a POST :)
It's one HTTP request per call, but requests usually flow over a persistent connection in HTTP 1.1 - it's certainly not re-opening a connection for every request.
TCP reconnection and stuff like that is at a lower level than Twirp. When you make a client of a Twirp service, the constructor accepts a http.Client which it'll use to send the requests. http.Client has a "Transport" field which is responsible for opening connections, that sort of thing. The Go standard library's defaults are pretty good, but you can tune it as you like.
Re: Twirp: A new RPC framework for Go
#20Hey everyone! I'm the OP and primary author of Twirp. I'm happy to answer any questions and hear feedback. You can also reach me directly, if you like, email is in my profile.
Thanks for posting! How did you work around issues with GRPC on AWS/ELB?
We tried grpc-gateway a little bit. But mostly, we wrote Twirp as a gRPC alternative because it was hard to work with ELBs.