A Kubernetes Lease Is Not a Fencing Token
Leader election tells you who should lead now. Distributed safety often requires a stronger property: stale leaders must be unable to perform authoritative work after failover.
Read articleArchitecture, security, and operations for delivering events to infrastructure that was never meant to accept inbound connections.
Leader election tells you who should lead now. Distributed safety often requires a stronger property: stale leaders must be unable to perform authoritative work after failover.
Read articleOwner references, Job TTLs, CronJob history and finalizers cover many cleanup jobs. The harder problem begins when cleanup becomes a cross-resource policy with protected classes and explicit ownership.
Read articleKubernetes gives us excellent primitives for scheduling, leases, secrets, health checks, networking and reconciliation. Building a distributed delivery system taught us where those primitives stop—and where application-level guarantees have to begin.
Read articleWebhooks push to public endpoints, but your services are private. Here is how outbound-only delivery works and what it means for security, reliability, and evidence.
Read articleRetries, dead-letter queues, idempotency, replay, and delivery evidence — the building blocks of reliable webhook infrastructure for private and critical-event workflows.
Read articleZen Mesh publishes claims and non-claims. Security claims require evidence. Partial evidence must be scoped.
Read articleDelivery logs show attempts and status codes—not verifiable proof of what was delivered, rejected, or observed in transit. Why evidence chains matter for compliance and AI-triggered workflows.
Read articleWebhooks are a push model in a world built to block inbound pushes. Here's why the usual fixes fall short—and what a separated control, data, and edge plane architecture looks like.
Read article