fix: replace busy-waiting with virtual threads to improve concurrency (issue #2977, #3446)

server-session/src/main/java/com/iluwatar/sessionserver/App.java

@@ -31,6 +31,9 @@
 import java.util.HashMap;
 import java.util.Iterator;
 import java.util.Map;
+import java.util.concurrent.Executors;
+import java.util.concurrent.ScheduledExecutorService;
+import java.util.concurrent.TimeUnit;
 import lombok.extern.slf4j.Slf4j;
 
 /**
@@ -57,6 +60,10 @@ public class App {
   private static Map<String, Instant> sessionCreationTimes = new HashMap<>();
   private static final long SESSION_EXPIRATION_TIME = 10000;
 
+  private static final ScheduledExecutorService sessionScheduler =
+      Executors.newSingleThreadScheduledExecutor(
+          Thread.ofVirtual().name("session-scheduler-", 1).factory());
+
   /**
    * Main entry point.
    *
@@ -86,7 +93,6 @@ private static void sessionExpirationTask() {
               while (true) {
                 try {
                   LOGGER.info("Session expiration checker started...");
-                  Thread.sleep(SESSION_EXPIRATION_TIME); // Sleep for expiration time
                   Instant currentTime = Instant.now();
                   synchronized (sessions) {
                     synchronized (sessionCreationTimes) {
@@ -110,7 +116,9 @@ private static void sessionExpirationTask() {
                   Thread.currentThread().interrupt();
                 }
               }
-            })
-        .start();
+            },
+            0,
+            SESSION_EXPIRATION_TIME,
+            TimeUnit.MILLISECONDS);
   }
 }

value-object/README.md

@@ -18,14 +18,16 @@ tag:
 
 ## Also known as
 
-* Embedded Value
 * Immutable Object
+* Embedded Value
 * Inline Value
 * Integrated Value
 
-## Intent of Value Object Design Pattern
+## Intent of Value Object / Immutable Object Design Pattern
 
-The Value Object pattern in Java creates immutable objects that represent a descriptive aspect of the domain with no conceptual identity. It aims to enhance performance and reduce memory overhead by storing frequently accessed immutable data directly within the object that uses it, rather than separately.
+The Value Object pattern (also known as the **Immutable Object pattern**) in Java creates immutable objects that represent a descriptive aspect of the domain with no conceptual identity. It aims to enhance performance and reduce memory overhead by storing frequently accessed immutable data directly within the object that uses it, rather than separately.
+
+The Immutable Object pattern ensures that an object's state cannot be modified after construction, providing thread-safety and predictability in concurrent scenarios.
 
 ## Detailed Explanation of Value Object Pattern with Real-World Examples
 
@@ -146,3 +148,4 @@ Trade-offs:
 * [J2EE Design Patterns](https://amzn.to/4dpzgmx)
 * [Patterns of Enterprise Application Architecture](https://amzn.to/3WfKBPR)
 * [ValueObject (Martin Fowler)](https://martinfowler.com/bliki/ValueObject.html)
+