State Management Patterns in Modern Signal-Based Angular
How signals change the calculus around state management in Angular, and when a plain service with writable signals is enough versus reaching for a store.
Tag
10 articles
How signals change the calculus around state management in Angular, and when a plain service with writable signals is enough versus reaching for a store.
How the strangler fig pattern lets you replace a legacy system incrementally behind a routing layer, avoiding the failure modes of a big-bang rewrite.
How to place error boundaries strategically in a React tree so a single failing widget degrades gracefully instead of blanking the entire page.
Why undocumented architectural decisions get relitigated endlessly, and how a lightweight ADR practice preserves the reasoning without becoming bureaucratic.
Multi-region architecture is sold as pure resilience, but the real trade-offs around data consistency, latency, and operational cost rarely make it into the pitch.
The real architectural differences between message queues and event streams, and why picking the wrong one causes problems that only show up under load.
Shopify rebuilt storefront rendering as a dedicated service to cut page load times, separating buyer-facing traffic from the core Rails monolith.
How an internal Bezos mandate requiring all Amazon teams to expose functionality only through service interfaces set up the conditions for AWS.
A 200ms response time target means nothing until it's broken down into a budget per component — otherwise every team assumes someone else owns it.
JPMS is easy to dismiss after a rough first encounter, but used selectively it solves real encapsulation problems the classpath never could.