Project Loom: Modern Scalable Concurrency for the Java Platform

Project Loom: Modern Scalable Concurrency for the Java Platform

Concurrent applications, those serving multiple independent application actions simultaneously, are the bread and butter of Java server-side programming. The thread has been Java’s primary unit of concurrency since Java’s inception, and is a core construct around which the entire Java platform is designed, but its cost is such that it can no longer efficiently represent a domain unit of concurrency, such as the session, request or transaction. As a result, Java has seen a proliferation of libraries and frameworks that offer scalable concurrency at the cost of abandoning the thread as the unit of software concurrency and, with it, the straightforward support of Java’s troubleshooting observability tooling, such as stack dumps, debuggers and profilers. Project Loom aims to reinstate the thread as an efficient unit of concurrency by adding a lightweight implementation of threads to the Java platform, which would allow straightforward code—that’s easy to write, understand and maintain, and works in harmony with the platform and its tooling—to scale and meet the requirements of even most demanding concurrent applications.

Ron Pressler, Consulting Member of Technical Staff, Oracle

[rajivkumar-ubuj]

Can't wait to have this feature. Good job guys 🔥🔥🔥👏👏👏

[kasparsr]

Project Loom is going to make or break the future of Java

[MatthewWaltersHello]

Excellent presentation.
I played around with Quasar library a few years ago. But the bytecode weaving was a turn-off for using in production.

But after dealing with the pain of writing and debugging reactive services, I'm excited to go back to good 'ol blocking code with Project Loom, as a part of the JDK this time.

[sede]

Absolutely fantastic and enlightening video. And the content is very exciting as well!! Thank you

[webfirmframework]

Very informative presentation, thanks for that.
Looking forward to its release.

[teevorian]

Wow, this is so ground breaking... wait, what year is this? 2020?

[manujbhalla]

In earlier readings on Loom, I got to know about "yield"ing control by thread and "continue" from where the last statement was. Are these implementation details of virtual threads?

[slr]

35:57 What version of Jetty did you use? My experience (with 3.1)is that it implements a pool on top of the executors' pool.

[vitalyparhomenko]

Is there any reason to use go lang after that? Kotlin/java + project loom = ❤️

[alexei]

Why Loom is not in Java 17? And when will it be?

[haseen]

The concept of virtual threads is similar to coroutines in Kotlin

[Scarrred]

Can you please post the presentation link? Thank you.

[MuztabaHasanat]

How will the virtual thread perform when it comes to the blocking io?

[tasoszervos]

Excellent material, terrible "upper body oscillation" delivery...
Not only terrible distracting visually, but also affects the audio. Perhaps a head mic could help here, instead of using a desk mic (assuming the "oscillation" can't be dealt with).

[java]

We’re just going to pretend that Kotlin coroutines haven’t been doing this on the jvm for years?