excon
Http Client
excon | Http Client | |
---|---|---|
1 | 3 | |
1,154 | 698 | |
0.2% | - | |
8.0 | 4.1 | |
29 days ago | 4 months ago | |
Ruby | Ruby | |
MIT License | Ruby License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
excon
-
Use Rails
A internal network boundary is probably worth it for heavy jobs, since you usually don't want it to interfere with serving web requests (no matter the tech).
You probably already know what I would say to each of those examples.
> Rails timing out after 30s while allocating 500MB of memory (mostly) in ActiveRecord to compute 5MB of JSON to return to an API caller.
I can make a JS or Go program perform the same way. In fact the exact same thing happened in my shop with Go/Gorm. The key question is: how do you compute the 5mb of JSON? The devil is in those details. We changed the way we computed ours, and the issue was gone.
> 90% of request latency of ~10s spent waiting for downstream services to respond to requests. Most of these could be fired off concurrently (ie `Promise.all` in node). 9s/10s this Rails worker is sitting around doing nothing and eating up ~300MB of memory.
This sounds broken. Why is the worker doing nothing for 9 out of 10s? But like I said earlier, there are a bunch of ways to use HTTP1.1 pipelining to run them concurrently. (https://github.com/excon/excon and https://github.com/HoneyryderChuck/httpx support it, but you can also do that with Net::HTTP I believe) And you can still start threads, which are still concurrent while blocking on IO.
> trying to extract out Authorization to a centralized service (so that other extracted services don't have to call into the monolith in order to make authorization decisions) is a major pain as the monolith now has to make calls out to the centralized auth system to in order to make authz decisions.
This seems unrelated to Rails. Not sure why monolith can't continue handling authorization.
Http Client
-
Turbocharge HTTP requests in Ruby
I think an implementation similar to this is built-in transparently to the oft-ignored ruby httpclient
-
The Best Ruby HTTP clients for 2021
I also don't know why these comparisons never include one of my favorites, HTTPClient. Although it's got some issues (pun intended) in it's maintenance/unclosed issues. :(
-
HTTP clients monthly benchmark
A fairly popular HTTP client that isnt included is httpclient
What are some alternatives?
Faraday - Simple, but flexible HTTP client library, with support for multiple backends.
RESTClient - Simple HTTP and REST client for Ruby, inspired by microframework syntax for specifying actions.
httparty - :tada: Makes http fun again!
Typhoeus - Typhoeus wraps libcurl in order to make fast and reliable requests.
Unirest - Unirest in Ruby: Simplified, lightweight HTTP client library.
HTTP - HTTP (The Gem! a.k.a. http.rb) - a fast Ruby HTTP client with a chainable API, streaming support, and timeouts
Sawyer - Secret User Agent of HTTP
Savon - Heavy metal SOAP client