pelikan
Pelikan is Twitter's unified cache backend (by twitter)
Finagle
A fault tolerant, protocol-agnostic RPC system (by twitter)
| pelikan | Finagle | |
|---|---|---|
| 4 | 24 | |
| 1,929 | 8,752 | |
| 0.1% | 0.1% | |
| 0.0 | 7.2 | |
| 7 months ago | 3 days ago | |
| C | 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.
pelikan
Posts with mentions or reviews of pelikan.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-12.
-
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).
- GitHub - twitter/pelikan: Pelikan is Twitter's unified cache backend
- Pelikan, Twitter‘s framework for building caches
-
NoSQL and Key-Value storage systems based on Rust (Redis and Tarantool replacements in Rust)
You forgot https://github.com/twitter/pelikan
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
What are some alternatives?
When comparing pelikan and Finagle you can also consider the following projects:
parity-db - Experimental blockchain database
gRPC - The Java gRPC implementation. HTTP/2 based RPC
lucid - High performance and distributed KV store w/ REST API. 🦀
Netty - Netty project - an event-driven asynchronous network application framework
CacheLib - Pluggable in-process caching engine to build and scale high performance services
OkHttp - Square’s meticulous HTTP client for the JVM, Android, and GraalVM.
rsedis - Redis re-implemented in Rust.
Akka - Build highly concurrent, distributed, and resilient message-driven applications on the JVM
PumpkinDB - Immutable Ordered Key-Value Database Engine
Finatra - Fast, testable, Scala services built on TwitterServer and Finagle
terminusdb-store - a tokio-enabled data store for triple data
Lagom - Reactive Microservices for the JVM