Finagle VS msdemos

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

You're not confined to the usual suggestions below (play, http4s). There's a ton of options. (I wrote test cases using a bunch of different frameworks a few years ago at https://github.com/hohonuuli/msdemos). Having written services using a variety of frameworks in production, I would strongly suggest using one that auto-generates API docs (openapi, swagger) for you. That will save you a huge amount of time later on. For heavier services, like the one at https://fathomnet.org/, I tend to the Java side (Quarkus is my current top choice, but Micronaut and Helidon are both great). For everything else I use Scala. My go-to right now is tapir using a vertx backend. See https://tapir.softwaremill.com/

I've put together simple examples (in Scala 3), that all do exactly the same thing, using various frameworks and benchmarked them. The source code is at https://github.com/hohonuuli/msdemos. For the record, I usually use Scalatra for Scala projects, Helidon or Micronaut for Java projects. If you're new and looking for something super simple, try out Cask or SparkJava.

I've written sample apps in Scala 3 that all do the same thing at https://github.com/hohonuuli/msdemos using akka-http (some issues at the moment), cask, finatra (which doesn't work with Scala 3), helidon, http4s, javalin, scalatra, sparkjava, vertx, and zio-http. I wrote those as an exercise in understanding particular frameworks and benchmarking them. (I write a lot of microservices). You can peruse the code there to get a feel for what it takes to write a service in a particular framework