fluvio VS sccache

I'm not quite sure how this compares to Kafka and fluvio [1], a Kafka competitor also written in Rust?

Is it more of a message queue like rabbitmq?

[1] https://www.fluvio.io/

Seeing signs of the hockey stick traffic on the Fluvio Open Source repo: https://github.com/infinyon/fluvio

Stopped the mobile notifications for the stargazer bot on discord and slack to stop the dopamine rush!!!

But thank you for checking us out.

Look at open source project fluvio https://github.com/infinyon/fluvio and see how we’re building a modern bus that can do ETL streaming style :).

Use icecream or sccache. sccache supports distributed builds.

https://github.com/mozilla/sccache/blob/main/docs/Distribute...

Worth noting that the first commit in sccache git repository was in 2014 (https://github.com/mozilla/sccache/commit/115016e0a83b290dc2...). So I suppose that what "happened" happened waay back.

If you have lots of shared dependencies, maybe try sccache?

I'm going to set up sccache [0] to use it tomorrow. We use MSVC, so EFS is off the cards.

[0] https://github.com/mozilla/sccache/blob/main/docs/S3.md

I think the primary benefit of pre-built procmacros will be for build servers which don't use a persistent cache (like sccache), since they have to compile all dependencies every time. But IMO improved support for persistent caches would be a better investment compared to adding support for pre-built procmacros.

Checkout https://github.com/mozilla/sccache

https://github.com/mozilla/sccache is another option which addresses the use cases of both icecream and ccache (and also supports Rust, and cloud storage of artifacts, if those are useful for you)

That being said a compilation cache, eg the de-facto standard for Rust: sccache (https://github.com/mozilla/sccache) will help to compile and store some of the build artifacts centralized - still for each crate version + build profile (RUSTFLAGS) combination.