Modern, Scalable Concurrency for the Java Platform [Re-Upload w/ proper audio]

preview_player
Показать описание
In this session learn about Project Loom, which aims to reinstate the thread as an efficient unit of concurrency by adding a lightweight implementation of threads to the Java platform.

⚠️ Note: This is a re-upload with the audio track fixed!

⎯⎯⎯⎯⎯⎯ Chapters ⎯⎯⎯⎯⎯⎯
00:00 Introduction
00:46 Why Loom exists?
07:15 Asynchronous Programming Style
10:08 Introducing Project Loom and Virtual Threads
12:09 How de we use Virtual Threads?
14:02 How can I limit Concurrent Access to a Limited Resource?
15:44 How do I know if I need Virtual Threads or Platform Threads?
17:00 High-level Implementation Concepts
18:00 What about Serviceability?
20:02 Structured Concurrency
21:52 Give Loom a try!

⎯⎯⎯⎯⎯⎯ Resources ⎯⎯⎯⎯⎯⎯

Categories: #Java #Loom #Concurrency
  1. Java
  2. Java programming language
  3. Java
  4. JDK
  5. JVM
  6. Java virtual machine
Рекомендации по теме
Project Loom: Modern 0:38:35

Project Loom: Modern Scalable Concurrency for the Java Platform

Modern, Scalable Concurrency 0:22:13

Modern, Scalable Concurrency for the Java Platform [Re-Upload w/ proper audio]

Project Loom: Modern 0:51:12

Project Loom: Modern Scalable Concurrency for the Java Platform By Alan Bateman

'Project Loom: Modern 0:59:51

'Project Loom: Modern Scalable Concurrency for the Java' - Ron Pressler

Project Loom: Modern 0:48:19

Project Loom: Modern Scalable Concurrency for the Java Platform — Ron Pressler

Alan Bateman — 1:12:40

Alan Bateman — Project loom: Modern scalable concurrency for the Java platform (ENG + RUS SUB)

How I scaled 0:13:04

How I scaled a website to 10 million users (web-servers & databases, high load, and performance)

FANG Interview Question 0:03:51

FANG Interview Question | Process vs Thread

Concurrency + Distribution 0:45:08

Concurrency + Distribution = Scalability + Availability (...) - Francesco Cesarini

Project Loom: Scalable, 1:23:40

Project Loom: Scalable, Harmonious Concurrency for the Java Platform

System Design: Why 0:03:39

System Design: Why is single-threaded Redis so fast?

Concurrency made easy 0:11:09

Concurrency made easy | System Design

[EN] Don't Wait 0:29:17

[EN] Don't Wait For Me! Scalable Concurrency for Ruby 3! / Samuel Williams @ioquatix

Node.js is a 0:08:18

Node.js is a serious thing now… (2023)

Concurrency + Distribution 0:43:31

Concurrency + Distribution = Scalability + Availability(...) - Francesco Cesarini

MongoDB in 100 0:02:27

MongoDB in 100 Seconds

Scaling Web Scraping: 0:07:17

Scaling Web Scraping: Concurrency vs Parallelism

Parallel Computing Explained 0:03:38

Parallel Computing Explained In 3 Minutes

Concurrency Oriented Programming 0:52:20

Concurrency Oriented Programming in a Modern World • Robert Virding & Francesco Cesarini • GOTO ...

Microservices Explained in 0:05:17

Microservices Explained in 5 Minutes

Loom Q&A plus 0:30:15

Loom Q&A plus some Structured Concurrency with Ron Pressler

C++ Concurrency TS 0:55:13

C++ Concurrency TS 2 Use Cases and Future Direction - Michael Wong, Maged Michael, Paul McKenney

Project Loom - 1:04:56

Project Loom - Scalable Concurrency with Virtual Java Threads

Why you Should 0:01:15

Why you Should NOT use Ruby on Rails

Комментарии
Автор

Great talk! Eagerly waiting for project loom to become production ready.

szquadri
Автор

Very informative presentation, thanks for publishing!

VisruthCV
Автор

When project loom started Ron's hair were black, thanks for your sacrifices Ron, Loom is greatest thing ever happened to Java. Next big thing i'm waiting is Project Leyden and jaotc's return.

ebuzertahakanat
Автор

This makes me think of GoLang, hope to see this integrated into the main JDK soon, seems very positive.

EmmTshh
Автор

When it will available for early access? I'm waiting for this from long time

rajivkumar-ubuj
Автор

I don't know how I feel about the whole structured concurrency thing. I'm curious whether it will be a forced or opt in thing. In Go, I can start a goroutine and let it run in the background doing its thing without being required to "join" it back into the goroutine that spawned it. If I do want structured concurrency, I can add it using tools from the standard library. But I'm open minded. Usually when I see a design pattern, it feels rigid at first until I start to see how it makes my life easier. Maybe having structured concurrency forced in Java will be like that.

user
Автор

Name of the compiler when we run the Java program?

rajeshn