In today’s world, applications run in increasingly complex and distributed environments. Growing data volumes and stringent performance requirements pose a challenge for developers—how do you scale, optimize speed, and still maintain code readability? In the presentation “Is Concurrency a Necessity?”, we’ll explore how Java, both in local applications and distributed systems, handles multithreading and asynchronous processing.

We’ll discuss Java’s built-in concurrency mechanisms (e.g., Thread, Executor, Future) along with popular libraries that facilitate multithreaded workloads (Reactor, Spring WebFlux, Quarkus). You’ll learn why the classic approach to multithreading may no longer suffice and how asynchronous programming shapes modern application design. We’ll also look at where code optimization ends and organizational challenges in distributed architectures begin—such as coordination, data consistency, and resilience against failures.

During the session, we’ll share best practices, design patterns, and lessons learned from years of working with multithreaded and distributed systems. By the end, we’ll answer the question: is concurrency truly a necessity in today’s projects, or rather a powerful tool to be used thoughtfully and with clear purpose?