Abstract
Most applications are based on the basic tenets of a call stack-based architecture: one method calls another one, and resumes execution when the called method completes. However, an increasing number of new components inside the Java platform introduce alternative, event-driven processing models. For example, the java.util.concurrent library in J2SE 5.0 introduces us to the notion of futures, executors and queues. In addition, many of the JMS and JAX-RPC libraries are based on asynchronous messaging models.
This talk examines the underlying principles behind event-driven architectures, demystifies concepts such as futures, and explains common patterns and best practices for non-call stack-based architectures. Finally, we will show how to re-architect a traditional, synchronous application to be more event-driven.
Date and Time
Audience
Novice
Speaker
