Storing only the current balance answers where you are, not how you got there. What Event Sourcing actually is, how state is rebuilt, and when CRUD is the better architecture.
A timeout does not tell you whether the server processed the payment. What an idempotent operation actually means, how retries duplicate effects, and how an Idempotency-Key makes a retry safe.
A check-then-act flow can sell the same seat twice. How atomic updates, constraints, locking, and idempotency keys keep exclusive resources consistent under concurrency.
JWT is a token format. An API key is a credential. This article shows how they differ, when each fits, and why a modern API can use both without picking a winner.
Microservices are not the required upgrade from a monolith. How to choose by domain, team, scale, and operational maturity — and what each choice actually costs.
Why a 30-day JWT is a bad session. How access tokens, refresh tokens, rotation, and revocation let a user stay signed in while limiting the lifetime of the credential that travels with every request.
Logging is not observability. How transactionId, traceId, and W3C Trace Context let you reconstruct a request across services — on Cloud Run, AWS, and Azure.
Pub/Sub is not a queue and not a REST replacement. How to design topics, subscriptions, retries, and idempotent consumers — and when HTTP or Cloud Tasks is the better fit.
The difference is the dependency model, not the CLI. How pnpm's store and isolated node_modules compare with npm and modern Yarn — and when each is the better fit.
What CORS, @nestjs/throttler, and Helmet actually protect in a NestJS API — and why none of them replace authentication, authorization, or input validation.
How to implement structured logs in NestJS with Pino so a payment is searchable by transactionId — the same identity the companion article separates from traceId.
OpenAPI is the contract. Swagger UI is the viewer. How NestJS builds an OpenAPI document from controllers and DTOs — and how to keep it honest in real teams.
Git is a local snapshot model. GitHub is the collaboration layer. How working trees, branches, merge, rebase, pull requests, and protection rules fit a real team workflow.