unix
5 minUnix Log Sorting: Normalize Offset Timestamps Before Ordering Events
Build a bounded investigation pipeline that preserves malformed records and avoids lexical sorting across mixed offsets.
Search the library
39 matching resultsArticles and interview answers
distributed systems
5 minEvent-Time Windows: Watermarks, Late Data, and Correctable Results
Design a minute-level dashboard that tolerates delayed events without treating a watermark as proof that every event arrived.
Q&A
Q&AWhat does a successful kubectl apply prove?
API acceptance is not convergence. Inspect rollout status, Pod conditions, and events to determine whether the desired workload is actually ready.
Read the concise answer
API acceptance is not convergence. Inspect rollout status, Pod conditions, and events to determine whether the desired workload is actually ready.
Q&A
Q&AHow does a transactional outbox make event publishing reliable?
Persist the business change and an event record together, then publish the event asynchronously.
Read the concise answer
A database transaction writes both the business state and an outbox row. A separate publisher retries delivery from that durable row. This avoids the gap where a database commit succeeds but broker publication fails. Delivery can still be repeated, so consumers should deduplicate by a stable event ID.
distributed systems
8 minCausal order: what a logical clock can and cannot tell you
Distinguish event causality from wall-clock order with Lamport and vector clocks.
databases
5 minSQL Event Gaps: LAG, Stable Ordering, and Explicit Window Frames
Investigate missing heartbeats with PostgreSQL interval arithmetic and a separate SQLite integer-millisecond contract.
http
6 minHTTP conditional writes: detect an edit based on stale state
Use strong validators and atomic preconditions to prevent lost updates without confusing them with retry identity.
Q&A
Q&AWhy is blocking JDBC dangerous inside a Spring WebFlux event loop?
A blocking call occupies a small Netty event-loop pool and stalls unrelated connections.
Read the concise answer
Reactive event loops depend on handlers returning promptly. Blocking JDBC parks the event-loop thread while it waits for the database, so many unrelated requests queue behind a few occupied threads. Use a reactive driver end-to-end or isolate unavoidable JDBC work on a bounded worker scheduler and constrain concurrency.