HTTP
excon
HTTP | excon | |
---|---|---|
6 | 1 | |
2,988 | 1,154 | |
0.1% | 0.2% | |
5.8 | 8.0 | |
12 days ago | 28 days ago | |
Ruby | Ruby | |
MIT License | MIT 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.
HTTP
-
Best Ruby HTTP Clients in 2023
Where's http.rb?
-
Pattern Matching Interfaces in Ruby
I had submitted a PR against this repo, but I believe the two most interesting types to match against are responses and requests:
-
My project: railstart app
http
-
7 Ruby Standard libraries you should get to grips with
In the past I have opted to use the HTTP.rb gem, but for simple tasks it’s really useful to learn Net/http or even open-uri for simple GET requests.
-
The Best Ruby HTTP clients for 2021
I actually like HTTP.rb's API more, but they still can't make a decision about "base URL" API, which is quite valuable for API wrappers, e.g. @client = HTTPLibrary.new('https://api.base.com/v2/') and then @client.get('/foo').
-
Ruby on Rails + Auth0: Authenticating your API with an external authentication service
Everything will be created under the class Auth0, and it'll be using HTTP gem to perform the quests, but feel free to decide over your code organization and tools.
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.
What are some alternatives?
Faraday - Simple, but flexible HTTP client library, with support for multiple backends.
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.
RESTClient - Simple HTTP and REST client for Ruby, inspired by microframework syntax for specifying actions.
XSR - XSR - eXtremely Simple REST client
Http Client - 'httpclient' gives something like the functionality of libwww-perl (LWP) in Ruby.
Savon - Heavy metal SOAP client