Jasp

We chose gRPC, not only for communication between microservices but also for communication between our mobile clients and our backend infrastructure.

We use buf.build to organize our proto files and to generate code in Typescript, Rust, and Kotlin that can then be consumed by our different applications.

It allows us to have a fully typed end-to-end communication protocol where versioning is made easy, unlike REST APIs. We have stricter control over how the data is accessed than GraphQL.

We hope that we will be able to take advantage of the streaming capabilities gRPC offers in the future too.

At Jasp, we're using a monorepo. Which means the source code of shared dependencies is in the same place as the apps that use them. We needed a tool to automate some of the tasks you usually do in a monorepo, such as building, testing, linting, typechecking. Being able to make sure you didn't break anything anywhere in the app with a simple command instead of waiting for a CI run makes our team more productive.

The fact that it does this in an optimized way, fetching results from previous runs if the source code has not changed, feels extremely satisfactory, since you can run a typechecking command on all your packages, but only those that have changed will actually get typechecked.