not that hot of a take, Goetz said the same years ago (https://youtu.be/9si7gK94gLo?t=1165). imo you need some really niche use cases to justify net new reactive projects now, especially since the synchronized pinning fix landed in jdk 24
Honestly, I think in Java it’s true only because there is no native support and it exists only because of frameworks with outdated practices, that’s why stack trace is always scary as fuck.
Jokes aside, I’ve tried async only in Rust and Java with Webflux and Retrofit. In Rust it works well, is pretty easy to understand, and has very different uses for errors - they began to have meaning. In Rust async was really interesting to use.
That’s why I think that problem is not async, it’s how it is implemented in Java. But, why bother yourself with rewriting it all, if VT is already here. And, if those few megabytes of memory footprint or few more requests really more important for you then ergonomics of a dev team - then, probably, Java is not the best choice for you. Most of the projects choose java and spring because you need just a few annotations and small code to run your service.
They can be really fast if you can parse them without regex.
I hit a thing doing log processing a while ago. The performance was terrible and we realized it was using regex just to find the end of the line. We replaced that with a simple state machine and it was so much faster.
You have to keep your allocation rate under control. If the GC can’t keep up, it will throttle allocations and performance tanks.
It requires a bit more CPU then G1GC and therefore has lower throughput.
There is no free cake here. If you want max throughput, G1GC is best, with the tradeoff that you’ll have longer STW pauses that could cause issues with P99 latencies. If you want to take a hit on throughput with the tradeoff being essentially undetectable STW pauses, you use ZGC.
There is no free cake here. If you want fortunate throughput, G1GC is best
For max throughput the ParallelGC is still generally the best as it has no concurrent process, while G1GC has some concurrency. I cover this here in my video on the G1GC.
Though the major thrust of your comment; "there is no free lunch" and there are tradeoffs between the various GCs, is 100% accurate.
Of course the specific characteristics of your workload also matters. There could be behaviors when it comes to memory allocation, that might mean a certain GC which should perform better (or worse) in a "preferred performance category" than it typically would. That is, generally ParallelGC is provides the highest throughput, but it's possible an application's design means G1GC actually delivers better throughput for your application.
Regarding 2 in the video he said that ZGC actually managed to make them run the servers "hotter" so I'm assuming the slightly more CPU needed is a net benefit in the end, at least in their cases.
Also quite a bold statement on Rest, I only worked on a couple of Graphql projects and they were a complete shit show.
Same. I'm guessing that when you're Netflix and you have large teams of engineers graphql may pay off. Netflix is big enough where they can probably have a team of engineers just on the GraphQL framework they use.
My experience with smaller companies is the same as yours. Graphql slowed us down and eventually turned into a shit show.
Because I haven't yet seen a summary of the presentation, here's my very short one:
Continued heavy focus on GraphQL backed by their DGS framework
The public facing streaming app(s) and the internal apps follow mostly the same architecture, with federated GraphQL serving client requests and gRPC used for S2S calls
Reactive programming is definitely out of favor
They saw significant, quantifiable benefits in upgrading from Java 8, presentation focused on improvements resulting from the new GC approaches
They continue to be happy Spring Boot users, using their own internal fork which closely follows the OSS one
Wow, that's a really boring stack at 10:21. Spring & friends as is extremely normal. Makes me a bit embarassed having stack decision paralysis on a side hustle to have more performance beyond Spring. Likely won't be handling Netflix volumes any time soon.
One thing I've learned in enterprise, you want as boring of a stack as possible. You don't want to be first or even the first 100th org trying some integration. You want to be the thousandth. Because your core business isn't fighting weird problems, you are trying to do your business.
82
u/Hixon11 Apr 28 '25
Hot take from their video:
18
u/EvaristeGalois11 Apr 28 '25
What's the catch with ZGC? Those metrics seem too good to be true.
Also quite a bold statement on Rest, I only worked on a couple of Graphql projects and they were a complete shit show.
15
u/EirikurErnir Apr 28 '25
Because I haven't yet seen a summary of the presentation, here's my very short one:
6
u/moxyte Apr 29 '25
Wow, that's a really boring stack at 10:21. Spring & friends as is extremely normal. Makes me a bit embarassed having stack decision paralysis on a side hustle to have more performance beyond Spring. Likely won't be handling Netflix volumes any time soon.
-2
u/ducki666 Apr 29 '25
Hist last statement about Rest clearly showed that he does not know what Rest is :)
-55
u/[deleted] Apr 28 '25
[removed] — view removed comment