concurrency23 articles

Java Virtual Threads, also known as lightweight threads, are a new feature in Java’s Project Loom that aim to simplify concurrent programming.

Virtual threads are lightweight implementations of java.lang.Thread, while this article turns the spotlight on the Continuations that are the basis of Virtual threads.

FEPCOS-J implements a Java-language extension that frees a Java-developer from network programming and supports cross-system concurrency.

Since there’s so much existing code using Enterprise Beans (EJB), a certain level of support is still desired. Piranha Cloud takes a somewhat novel approach to Enterprise Beans and maps Enterprise Beans annotations to equivalent functionality in CDI or other Jakarta EE APIs.

EJB, or Enterprise Beans, are Java classes with a number of container provided services attached to them, such as transactions, remoting and security. A possible future direction for EJB is to rebase it on CDI. Instead of having those two essentially competing component models in Jakarta EE, we would end up with just one.

Project Loom aims to fix issues in the current concurrency model by introducing two new features: virtual threads and structured concurrency.

Java Concurrency is a small fundamental spec under the Jakarta EE umbrella. As project lead, here’s what it is, its future, and how to be involved!

Even while threads are helpful, they are dreadful to many developers. Here are five essential threading concepts for Java developers!

Jakarta Concurrency is a small, but fundamental, specification under the Jakarta EE umbrella. As project lead, I provide more information on what it is.

What is the maximum number of worker threads we can put in a ThreadPool? Let’s find out today on Foojay’s amazing Java threading series!