weaver VS Quarkus

> trying to hide distribution

The paper unfortunately hides that in reality you have to pass a context object in your RPC calls, hence there is no ambiguity whether you are calling a potentially remote object.

It's in the example on the project home page: https://serviceweaver.dev/

  // The "RPC" handler

Service Weaver is an open source programming framework from Google that allows you to write a Go application as a modular binary and deploy it as a set of connected microservices.

Boneless is a powerful tool that offers a wide range of features to facilitate application development. In this blog post, we will explore some essential tools that can be used in conjunction with Boneless: Service Weaver, Go Migrate, SQLC, and Fiber. Let's discover how these tools can boost productivity and efficiency in application development.

I assume you’re already aware of https://serviceweaver.dev/ Someone’s got to do it, so let that be Google.

Meanwhile, if you're building something smaller than Netflix, I'm writing a book just for that (https://opinionatedlaunch.com/).

It's about mobile apps, but I talk about backend at great length, especially since my background is Java. The book is called "opinionated" because I cover Quarkus (https://quarkus.io/), monolith, Fly.io, and no K8s.

Quarkus is a Java based framework tailored for GraalVM and HotSpot, which results in an amazingly fast boot time while having an incredibly low memory footprint. It offers near instant scale up and high density memory utilization which can be very useful for container orchestration platforms like Kubernetes or Serverless runtimes like AWS Lambda.

Other useful articles related to Quarkus extension development can be found under the Writing Extensions guide category on the Quarkus.io website.

Quarkus is one of Java frameworks for microservices development and cloud-native deployment. It is developed as container-first stack and working with GraalVM and HotSpot virtual machines (VM).

If you GraalVM Native Image or one of the frameworks based on it then bootstrap cost disappears:

https://quarkus.io

We are open to practice using any open-source project, however, we want to set a sharp focus on projects maintained by the Red Hat, and our own projects in the Caravana Cloud organization on github. If there is no reason to do differently, we'll build using technologies such as OpenShift, Quarkus, Ansible and related projects.

The Quarkus you are talking about is this one? https://quarkus.io/