sade.dev
TREN

Systems

Systems

Architecture decisions as a whole, and the reasoning behind them.

  1. 10 sections

    Transactional Outbox: Dual-Write, At-Least-Once, and Idempotent Consumption

    Writing to the database but failing to put the event on the queue: closing dual-write with an outbox, suppressing the at-least-once repeats it creates, and encrypting the field.

    #architecture#messaging#idempotency#reliability#security
  2. 7 sections

    GPU FinOps with eBPF

    Why GPU spend is invisible to cgroup and cAdvisor metrics, and how eBPF attributes GPU time and memory to teams for chargeback — with the honest limit at the CUDA boundary that DCGM has to cover.

    #ebpf#gpu#finops#observability#kubernetes
  3. devrazziSkip 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.
  4. 6 sections

    Zero Static Authority in Multi-Cluster GitOps

    GitOps across many Kubernetes clusters with no long-lived kubeconfig or token. SPIFFE IDs, SPIRE-issued short-lived SVIDs, trust-domain federation — the order to build it in, and what each step costs.

    #kubernetes#gitops#spiffe#security#architecture
  5. 5 sections

    Distributed Tracing Across a Polyglot Queue

    A message crosses PHP, Go and Python over a frozen envelope. Turning its journey into one OpenTelemetry trace with no new field and no core dependency — and the honest limit of that.

    #opentelemetry#observability#distributed-tracing#messaging#architecture
  6. 10 sections

    Race Conditions and Gaps in Sequential Numbering: JIT Reservation

    Generating legally sequential, gap-free numbers with parallel workers: the JIT reservation pattern that solves race conditions and gaps together

    #architecture#production#concurrency#queue#idempotency
  7. 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 and a separate data layer — the breaking points in order, and what each one costs

    #postgresql#architecture#production#scaling#replication
  8. 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.

    #vps#architecture#nginx#postgresql#redis
  9. 13 sections

    Laravel Production Stack

    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

    #laravel#php#production#architecture

Search

Start typing. Notes, systems, journal, tools and pages.

↑↓move↵openescclose