Search the library

Search concepts, questions & guides

Topic

9 matching resultsArticles and interview answers

Q&A

Why are Kafka offsets and commit timing so important?

Offsets are the durability checkpoint. Commit too early and you lose work; commit too late and you duplicate it.

Read the concise answer

Kafka commits represent when the consumer believes work has been finished. If the offset is committed before the business effect is truly durable, a crash can lose data. If it is committed only after a delay, the application may re-process messages when the consumer restarts. The correct strategy is to commit only after the state change is stored successfully and the work is idempotent enough to recover from retries.

unix

5 min

Unix Log Sorting: Normalize Offset Timestamps Before Ordering Events

Build a bounded investigation pipeline that preserves malformed records and avoids lexical sorting across mixed offsets.

python

5 min

Python Event Times: Normalize Offsets Without Losing Elapsed Time

Build a small timestamp boundary that rejects naive input, normalizes aware values, and measures latency with the right clock.

distributed systems

12 min

Kafka Consumer Groups: Architecture & Common Pitfalls

Consumer groups are the mechanism that turns Kafka partitions into scalable, failure-tolerant work units. Learn how rebalances, offsets, and lag interact under load before you ship your first serious pipeline.

java

5 min

Java Appointment Times: Resolve DST Gaps and Overlaps Explicitly

Turn a local appointment into an instant without silently shifting nonexistent times or choosing an ambiguous offset.

Q&A

Why does a byte offset alone not make a download safe to resume?

The representation may have changed since the saved prefix was downloaded.

Read the concise answer

Use a validator such as a strong ETag with If-Range, validate the 206 Content-Range before append, and verify final integrity separately. An ETag is not necessarily a cryptographic digest.

databases

19 min

Database Internals Advanced: MVCC Anomalies, Cost Models, Sharding, and Storage Engines

Reason about isolation anomalies, query-plan mistakes, B-tree/LSM trade-offs, shard routing, and production-safe index changes.

http

8 min

HTTP range requests: resume transfers without stitching different files

Use validators, Content-Range, and 416 handling to make partial downloads coherent.