Systems & architecture
10 posts tagged #architecture on DiCodeWeb, from fundamentals to production, newest first.
10 postsUpdated Oct 11, 2026
How I run practical threat modeling with a product team: the four questions, a data flow diagram with trust boundaries, STRIDE per element on a real system with an SPA, API, Postgres, S3 uploads, a payment webhook and an admin panel, simple risk rating, threats turned into tickets, and a threat model that lives in the repo.
Event Storming is the bridge between business analysis and software design. This post covers the three workshop levels, the sticky-note grammar, facilitation, a real clinic booking example, finding bounded contexts, context mapping, and turning the result into aggregates, commands and events in NestJS.
Micro-frontends solve an organizational problem — independent teams shipping independently — not a technical one. This post compares five ways to compose a frontend, digs into Module Federation 2.0 (shared singletons, version skew, manifests, types, fallbacks) and shows when a Turborepo monorepo is the better answer.
"use client" doesn't mark a kind of component; it marks where the client graph begins. This post rebuilds the mental model for RSC in Next.js 16: what crosses the boundary, where data fetching belongs, waterfalls, streaming, and the mistakes that bloat bundles or leak data.
What NestJS does under the hood — the order of middleware, guards, interceptors, pipes and filters; DI, scopes and durable providers; dynamic modules — and how to use it to structure a large API as a clean modular monolith with a consistent error model, request context and graceful shutdown.
How signals track dependencies, why push-pull gives glitch-free updates, how Solid, Preact, Angular and Vue use them, where the TC39 proposal stands, what the React Compiler changes, and the production pitfalls — with a tiny signal implementation in TypeScript.
Frontend apps break when we design them page by page. A short field guide to mapping state, data flow and ownership before drawing the UI.
Optimistic updates with rollback, an IndexedDB-backed outbox, idempotency keys, retrying when the network returns, conflict resolution strategies, showing sync status and testing offline scenarios.
Feature flags decouple deploy from release, but used carelessly they turn into tech debt and flickering UIs. This post covers the four kinds of flags, evaluating on the server vs the client, typed flag definitions in TypeScript, gradual rollout, A/B testing and a cleanup process.
Why isLoading, isError and data living side by side breed bugs, how to model UI as states and events, a typed useReducer state machine for a submit flow, and when a statechart library is worth it.