Finagle
mux
Finagle | mux | |
---|---|---|
24 | 86 | |
8,755 | 17,948 | |
0.1% | - | |
7.2 | 2.6 | |
7 days ago | over 1 year ago | |
Scala | Go | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" 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.
Finagle
-
Features of Project Loom incorporated in Java 21
Not sure about now but a few years back the company I worked for was heavily vested in Finagle [1] using Future pools. I'm sure virtual threads would only enhance this framework. Also, Spring and it's reactive webflux would probably benefit as well [2].
[1] https://twitter.github.io/finagle/
[2] https://docs.spring.io/spring-framework/reference/web/webflu...
- Twitter Finagle: Backoff.scala
-
Twitter (re)Releases Recommendation Algorithm on GitHub
Don't really see how "enterprise scala" has anything to do with this, scala is meant to be parallelized , that's like it's whole thing with akka / actors / twitter's finagle (https://twitter.github.io/finagle/)
-
We switched from Scala 2 to Rust
So biased. Twitter dropping Scala3 is simply untrue, ticket is there and still is open https://github.com/twitter/finagle/issues/932
-
Introduction to Bazel for Scala developers
Thank you. I only took a quick look, but this looks like a goldmine of info if you are interested in using bazel to build a scala monorepo: https://github.com/twitter/finagle
-
Server Stack Options for Scala
Finagle
-
Elon: "[Twitter's] recommendation algorithm was using absolute block count, rather than percentile block count, causing accounts with many followers to be dumped, even if blocks were only 0.1% of followers."
And the engineering team are far from imbeciles because they built one of the worlds' best cache and RPC microservice components. As well as the fact that up until Musk took over the website was running just fine (other than your issue with product decisions).
-
Pretty incredible thread where Elon confuses how GraphQL works, thinks the Android client itself is making one thousand requests, and then publicly fires an employee who corrects him.
Bro it's their fucking project lolhttps://twitter.github.io/finagle/
-
Elon Musk publicly feuding with and firing his developers on Twitter
RPC generally means server side calls, probably this https://twitter.github.io/finagle/, and XHR is not RPC.
-
Pretending to know what you're talking about
not familiar with twitter internals but it would be atypical to use gql for internal communications even if you expose it as a public api. twitter also develops a widely-used RPC system https://github.com/twitter/finagle
mux
-
From Homemade HTTP Router to New ServeMux
This is not a disproval, but gorilla/mux has comparatively poor benchmark results among popular (many stars) third-party HTTP routers. , used by many users.
-
How AuDHD traits have helped me get good at devrel
This attention to detail also can mean that for key abstractions in a tool or framework, what concretely goes on doesn't go unexplained. For example, when I was learning Go for web development, my first stumbling block was understanding how interfaces worked, particularly http.Handler, which is key to doing web development with Go's powerful net/http package and the fits-like-a-glove package built on top of it, the Gorilla Mux router. My way of finding out how that worked, and seeing the elegance of that interface, was pretty unorthodox - I figured out how Handlers worked by looking directly at Go's source code (which also is a demonstration of Go's readability, if you're interested in joining the Gophers!). And coming out of that was my very first tech talk at in 2015, on learning Gorilla from its Node.js counterpart, Express.js!
-
Microservices Authentication and Authorization Using API Gateway
In this ApiGateway implementation, we've employed the Gorilla Mux router for enhanced route handling. Let's break down the key components:
- The Gorilla web toolkit project is being revived, all repos are unarchived now
- The Gorilla web toolkit project is being revived, all repos are out of archive mode.
-
How to build an API using Go
Now that we have set up the Go environment, we can start building our API. The first step is to choose a framework. There are several popular frameworks for building APIs in Go, such as Gorilla mux, Echo, and Gin. For this article, we'll use Gorilla mux.
-
go-mir - a toolkit to develop RESTful API backend service like develop service of gRPC
Mir is a toolkit to develop RESTful API backend service like develop service of gRPC. It adapt some HTTP framework sush as Gin, Chi, Hertz, Echo, Iris, Fiber, Macaron, Mux, httprouter。
-
I've just started learning Golang, and I'm struggling to choose a framework.
My personal favorite tools: - https://github.com/go-kit/ for building services (although it's not necessary a great tool for prototyping) - https://github.com/gorilla/mux router (although it's been recently deprecated, so I'm looking for a similar, maintained library) - https://entgo.io/ ORM - https://watermill.io/ for messaging
-
mux VS Don - a user suggested alternative
2 projects | 15 Mar 2023
-
Using Redis Caching and the Redis CLI to Improve API Performance
We will be using Gorilla Mux to create the APIs locally. Gorilla Mux implements a request router and dispatcher to match the incoming requests.
What are some alternatives?
gRPC - The Java gRPC implementation. HTTP/2 based RPC
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
Netty - Netty project - an event-driven asynchronous network application framework
Fiber - ⚡️ Express inspired web framework written in Go
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
Echo - High performance, minimalist Go web framework
Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM
chi - lightweight, idiomatic and composable router for building Go HTTP services
Finatra - Fast, testable, Scala services built on TwitterServer and Finagle
httprouter - A high performance HTTP request router that scales well
Lagom - Reactive Microservices for the JVM
fasthttp - Fast HTTP package for Go. Tuned for high performance. Zero memory allocations in hot paths. Up to 10x faster than net/http