excon
Avalonia.Markup.Declarative
excon | Avalonia.Markup.Declarative | |
---|---|---|
1 | 6 | |
1,154 | 234 | |
0.2% | 8.6% | |
8.0 | 7.0 | |
29 days ago | 13 days ago | |
Ruby | C# | |
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.
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.
Avalonia.Markup.Declarative
What are some alternatives?
Faraday - Simple, but flexible HTTP client library, with support for multiple backends.
Comet - Comet is an MVU UIToolkit written in C#
httparty - :tada: Makes http fun again!
Maui.Markup - The .NET MAUI Markup Community Toolkit is a community-created library that contains Fluent C# Extension Methods to easily create your User Interface in C#
Typhoeus - Typhoeus wraps libcurl in order to make fast and reliable requests.
Avalonia.FuncUI - Develop cross-plattform GUI Applications using F# and Avalonia!
RESTClient - Simple HTTP and REST client for Ruby, inspired by microframework syntax for specifying actions.
GitTrends - A iOS and Android app to monitor the Views, Clones and Star history of your GitHub repos
Http Client - 'httpclient' gives something like the functionality of libwww-perl (LWP) in Ruby.
Eto.Forms - Cross platform GUI framework for desktop and mobile applications in .NET
HTTP - HTTP (The Gem! a.k.a. http.rb) - a fast Ruby HTTP client with a chainable API, streaming support, and timeouts
RoadCaptain - Build and ride custom routes in Zwift