We mistook event handling for architecture

"Events are essential inputs to modern front-end systems. But when we mistake reactions for architecture, complexity quietly multiplies. Over time, many front-end architectures have come to resemble chains of reactions rather than models of structure. The result is systems that are expressive, but increasingly difficult to reason about."

"Instead of organizing systems around chains of reactions, some teams are starting to treat application state as the primary structure of the system. In this model, events still occur, but they no longer define the architecture; they simply modify state. The UI and derived behavior follow from those relationships."

"Front-end engineering runs on events. User interactions, network responses, timers, and streaming data constantly enter our applications, and our systems are designed to respond to them. Events are unavoidable; they represent moments when something changes in the outside world."

Modern front-end systems rely on events as essential inputs, but treating reactions as architecture creates unnecessary complexity. Many applications have evolved into chains of reactions rather than structured models, making them difficult to reason about despite their expressiveness. A new architectural perspective treats application state as the primary system structure, with events serving only to modify state rather than define architecture. The UI and derived behaviors follow from state relationships. This state-first approach provides clearer reasoning for increasingly complex applications. Front-end engineering has become sophisticated in event processing through streams, side effects, and reactive pipelines, but this sophistication shifted from being a mechanism to becoming architecture itself, fundamentally changing how systems are conceptualized.

Read at InfoWorld