Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Unidirectional Data Flow in Angular: Signals, input/output and State in Services
Unidirectional data flow in Angular means the state has a single owner, data goes down with input(), change requests go up with output(), and derived values are computed with computed(). With real tests we show how state written by an effect lags behind, how model() bypasses a business rule and why default OnPush misses an array changed in place, then move the state into a service that holds signals.
Flux and Unidirectional Data Flow: Why Didn't Two-Way Binding Scale?
Two-way binding and observable models that update each other produce cascading updates whose result depends on listener order, plus intermediate states that were never valid (glitches); Flux solved this with a one-way flow (action → dispatcher → store → view). We show the glitch with real output on the same order form, cover Redux's three principles and the Elm Architecture, write a 40-line TypeScript store and weigh the cost of immutability and boilerplate.