Finagle VS twemproxy

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...

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/)

So biased. Twitter dropping Scala3 is simply untrue, ticket is there and still is open https://github.com/twitter/finagle/issues/932

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

Finagle

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).

Bro it's their fucking project lolhttps://twitter.github.io/finagle/

RPC generally means server side calls, probably this https://twitter.github.io/finagle/, and XHR is not RPC.

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

Lol, this alone says you don’t have any idea about working on large scale system. The reason behind working on the open source project is that a lot time, these open source project are being used in the company's system and have issues that need to be solved. Open source projects are not some magic that scale automatically. Obviously if you work on small scale where you never need to push a system , you will never see these issue, But the only you have a seamless experience using because some other developers have worked on it. A lot of time when you work on a large system, you will encounter problems that don’t have a solution, so the option is either solve it in the open source system or develop a new one ( like finagle). For example look at https://github.com/twitter/twemproxy, which was created 8 years ago. tell me what other solution existed that could have solved this at that time ?

I wanted to try twemproxy for connection pooling, but it doesn't support all redis commands, and it even fails at 'cache:clear' because it does not support FLUSHDB, which cache:clear requires. Is anyone running laravel and redis with twemproxy, and if so how? Or maybe some other solution to enable connection pooling.

Shit, I thought you were spouting nonsense jargon, but nope - twemproxy is a real thing: https://github.com/twitter/twemproxy

Also, you conveniently ignored the two other major projects https://github.com/twitter/twemproxy and https://github.com/twitter/finagle , which are tremendously popular and are the major building block of lots of large scale systems.

Twemproxy is an open source proxy server created by Twitter and is one of the methods recommended by Google for managing a cluster of Memorystore instances in GCP (Google Cloud Platform). Memorystore is the managed service provided by GCP for application caching with either Redis or Memcached. Twemproxy provides a way to evenly distribute cached data between multiple Redis instances to improve the performance, reliability, and resilience of a distributed system.