Rust vs. JVM: Adjustments following organizational restructuring

After over two years of using Rust within my team, my company has undergone significant restructuring. This resulted in the reduction of my team to just two other developers skilled in Rust. During an external evaluation of each team's maturity level, our use of Rust was highlighted as a potential bottleneck, with a recommendation to switch to a JVM language, specifically Java, due to the ease of finding JVM developers compared to Rust specialists. Transitioning to a JVM language would require a complete rewrite of our projects and the disbanding of our current team, as none of us possesses senior knowledge of any JVM language. I have been tasked with outlining scenarios for continuing with Rust, including potential risks, especially now that we are reduced to two developers. Our projects obtain approximately 25k lines of Rust code in active use.

I would like to receive feedback on the advantages and risks of Rust versus JVM languages like Java or Kotlin. Our initial choice of Rust was driven by its performance and cost-effectiveness, particularly in the context of AWS Lambda. Personally, I find Rust's emphasis on explicit coding practices enhances maintainability compared to languages like Java or PHP, which I have worked with over the past two decades.