https://devops-monk.com/tags/non-blocking/Recent content in Non-Blocking on Devops MonkHugoen-usMon, 04 May 2026 00:00:00 +0000https://devops-monk.com/tutorials/java8/completablefuture/Mon, 04 May 2026 00:00:00 +0000https://devops-monk.com/tutorials/java8/completablefuture/The Problem with Future<T> Java 5 introduced Future<T> for async computation. The problem: you can only get the result by calling get(), which blocks: // Java 7 ExecutorService pool = Executors.newFixedThreadPool(4); Future<User> future = pool.submit(() -> fetchUser(userId)); // ... User user = future.get(); // BLOCKS until done If you have multiple async operations that depend on each other, you end up with a chain of blocking get() calls — effectively synchronous execution with extra overhead.