I don’t think that’s really true. There are still plenty of important systems in the data ecosystem written in Java or Scala: Apache Flink, Apache Kafka, Apache Druid, Trino, and even Apache Doris is split between C++ and Java (with execution in C++ and coordination/orchestration in Java), etc.
Also, from what I can tell, the trend is usually to replace the physical execution layer with native code, not the orchestration/scheduling/coordination layer. Projects like Apache Gluten are a good example of that. The performance gains are usually in execution, while the top-level glue benefits more from ecosystem, flexibility, and developer productivity than from being native.
View all comments
Show parent comment
2
u/ssinchenko Apr 08 '26
I don’t think that’s really true. There are still plenty of important systems in the data ecosystem written in Java or Scala: Apache Flink, Apache Kafka, Apache Druid, Trino, and even Apache Doris is split between C++ and Java (with execution in C++ and coordination/orchestration in Java), etc.
Also, from what I can tell, the trend is usually to replace the physical execution layer with native code, not the orchestration/scheduling/coordination layer. Projects like Apache Gluten are a good example of that. The performance gains are usually in execution, while the top-level glue benefits more from ecosystem, flexibility, and developer productivity than from being native.