network
Micro Communication Protocol (MUCP) (by micro)
Finagle
A fault tolerant, protocol-agnostic RPC system (by twitter)
network | Finagle | |
---|---|---|
3 | 24 | |
20 | 8,752 | |
- | 0.1% | |
4.6 | 7.2 | |
11 days ago | 7 days ago | |
Go | Scala | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
network
Posts with mentions or reviews of network.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-02.
-
Ask HN: Why isn't JSON-RPC more widely adopted?
So funny you say this. I think it's the insight of many developers including my own. I hacked together a framework that did this before the existence of GRPC. Now I'm trying to formalise it as a protocol. https://github.com/micro/network/blob/main/PROTOCOL.md
-
More Instant Messaging Interoperability
Alright, let me throw my hat into this ring with a totally unfinished idea. I started working on a design for something called the Micro Communication Protocol (MUCP) [1]. It's a header based protocol that's transport agnostic and focuses on service-to-service communication. An early prototype existed in Micro [2] but I'm primarily focused on redesigning the protocol before re-implementing it. Micro was geared towards API first services but I'm looking to expand the scope and try to build a UI layer on top. Most of the protocols focused very much on communication between people but I think if you focus on service-to-service communication more broadly it opens up the avenue to all sorts of multiplayer collaboration.
- [1] https://github.com/micro/network/blob/main/PROTOCOL.md
-
Real World Micro Services
Yea like you're part of this club that has exclusive access to something, you contribute to it, deliver value, see it grow and then it's gone when you leave. It exists within a silo and for the better part of a decade that's really irked me but I haven't quite figured out how to solve for that problem beyond doing it in a shared open source repo and a shared platform. I think I the issue is it's bigger than any one person and you have to find a way to sell thousands of people on the idea. My starting point was code and now I wonder could I have approached this differently? Is there another path in which this would actually succeed? I'm still trying to figure it out and it's driving me crazy. Next I'll be writing a protocol no joke https://github.com/micro/network
Finagle
Posts with mentions or reviews of Finagle.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-15.
-
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