Systems
Architecture decisions as a whole, and the reasoning behind them.
- 10 sections
Transactional Outbox: Dual-Write, Idempotent Consumers
Closing dual-write with an outbox, suppressing the at-least-once repeats it creates, and encrypting the personal data inside the event.
- 7 sections
GPU FinOps with eBPF
Why GPU spend is invisible to cgroup and cAdvisor metrics, how eBPF attributes it to teams — and the CUDA boundary only DCGM can cover.
- SponsoreddevrazziSkip the noise, read the signalCurated tech news and synthesis for developers. The content is produced by AI agents, and every piece links back to its source.
- 6 sections
Zero Static Authority in Multi-Cluster GitOps
Multi-cluster GitOps with no long-lived kubeconfig: SPIFFE IDs, SPIRE-issued short-lived SVIDs — the order to build it in, and what each step costs.
- 5 sections
Distributed Tracing Across a Polyglot Queue
Turning a message that crosses PHP, Go and Python over a frozen envelope into one OpenTelemetry trace — no new field, no new dependency.
- 10 sections
Race Conditions and Gaps in Sequential Numbering
Generating legally sequential, gap-free numbers with parallel workers: the JIT reservation pattern that solves race conditions and gaps together
- 9 sections
Scale Breaking Points in Data-Intensive Systems
As data load grows, where does boring architecture break? Working set, read replicas, partitioning, write load, a separate data layer — in order.
- 11 sections
Multiple Projects on a Single VPS
One VPS, several independent apps. Deliberate minimalism over Kubernetes: user isolation, separate PHP-FPM pools, shared PostgreSQL/Redis, a plain deploy.
- 13 sections
Laravel Production Stack: Why Each Piece Is There
A production-grade Laravel setup with Nginx + PHP-FPM + Redis + PostgreSQL + Supervisor + Horizon. Each piece's job and what you lose if you drop it